[arch-general] Issues with torrents
First of all, I don't know if this is the right place to ask such a question, so excuse me if it turns to be it isn't. Some days ago I realized that most of my torrents (mostly related to the openbittorrent tracker but also including another ones (The arch iso torrent works, though) ) fail to download. The information about how many seeders/leechers are is displayed, but the count of how much seeders I'm connected to remains 0 and no download happens. In my low knowledge of troubleshooting networking issues I've tried to ping those trackers that are giving me problems, getting on all of them a 100% packet loss. Also, traceroute is not able to give me a full route of the packets. I've tried to flush my pdnsd cache, change dns but I keep getting the same result after repeating the above I ask on this mailing list because I'm experiencing this on both my home connection and at the university so I thought It could be something related to my computer or something in common in both connections. I don't know and I'm completely lost in this. Should I assume that this is something beyond my reach and try to live with it while it gets solved on another level? Thank you in advance
[2012-10-25 12:57:18 +0200] Alexandre Ferrando:
Some days ago I realized that most of my torrents (mostly related to the openbittorrent tracker but also including another ones (The arch iso torrent works, though) ) fail to download. The information about how many seeders/leechers are is displayed, but the count of how much seeders I'm connected to remains 0 and no download happens.
I cannot understand how you would expect a useful answer without giving us at the very least the name of your torrent client and of your ISP... -- Gaetan
On 25 October 2012 13:07, Gaetan Bisson <bisson@archlinux.org> wrote:
[2012-10-25 12:57:18 +0200] Alexandre Ferrando:
Some days ago I realized that most of my torrents (mostly related to the openbittorrent tracker but also including another ones (The arch iso torrent works, though) ) fail to download. The information about how many seeders/leechers are is displayed, but the count of how much seeders I'm connected to remains 0 and no download happens.
I cannot understand how you would expect a useful answer without giving us at the very least the name of your torrent client and of your ISP...
-- Gaetan
Oh, sorry. Torrent clients I've tried: Deluge and aria2c ISPs: ONO (spanish) and the university's ISP seems to be the university itself, Universidad Politecnica de Valencia
On 25/10/12 13:13, Alexandre Ferrando wrote:
On 25 October 2012 13:07, Gaetan Bisson <bisson@archlinux.org> wrote:
[2012-10-25 12:57:18 +0200] Alexandre Ferrando:
Some days ago I realized that most of my torrents (mostly related to the openbittorrent tracker but also including another ones (The arch iso torrent works, though) ) fail to download. The information about how many seeders/leechers are is displayed, but the count of how much seeders I'm connected to remains 0 and no download happens. I cannot understand how you would expect a useful answer without giving us at the very least the name of your torrent client and of your ISP...
-- Gaetan Oh, sorry.
Torrent clients I've tried: Deluge and aria2c ISPs: ONO (spanish) and the university's ISP seems to be the university itself, Universidad Politecnica de Valencia I've a similar issue like you with Deluge. A post that describes what I see in my /var/log: https://bbs.archlinux.org/viewtopic.php?id=123807
|[...] TCP: Possible SYN flooding on port 53126. Dropping request| [...] A workaround in this case it's disabling SYN flood protection in the kernel, adding to /etc/sysctl.conf net.ipv4.tcp_syncookies=0 but it's not a real solution. $(Figue)
On 25 October 2012 23:03, Figue <ffigue@gmail.com> wrote:
I've a similar issue like you with Deluge. A post that describes what I see in my /var/log: https://bbs.archlinux.org/viewtopic.php?id=123807
|[...] TCP: Possible SYN flooding on port 53126. Dropping request| [...]
I don't have any messages like that on my logs.
A workaround in this case it's disabling SYN flood protection in the kernel, adding to /etc/sysctl.conf net.ipv4.tcp_syncookies=0
That doesn't help. I'm starting to think this is ISP related.
On Thu, Oct 25, 2012 at 11:31 PM, Alexandre Ferrando <alferpal@gmail.com> wrote:
On 25 October 2012 23:03, Figue <ffigue@gmail.com> wrote:
I've a similar issue like you with Deluge. A post that describes what I see in my /var/log: https://bbs.archlinux.org/viewtopic.php?id=123807
|[...] TCP: Possible SYN flooding on port 53126. Dropping request| [...]
I don't have any messages like that on my logs.
A workaround in this case it's disabling SYN flood protection in the kernel, adding to /etc/sysctl.conf net.ipv4.tcp_syncookies=0
That doesn't help. I'm starting to think this is ISP related.
Universities networks often block torrent protocol on the proxy level. Also recently (last 2 years) with all that fuzz on torrents and piracy, ISPs usually sniff package traffic and throttle torrents also. Alternative ways have been proposed, search if your ISP is blocking the torrents and what you could do to work around it. -- Caution: breathing may be hazardous to your health. #include <stdio.h> int main(){printf("%s","\x4c\x65\x6f\x6e\x69\x64\x61\x73");}
On 26 Oct 2012 09:27, "Leonidas Spyropoulos" <artafinde@gmail.com> wrote:
On Thu, Oct 25, 2012 at 11:31 PM, Alexandre Ferrando <alferpal@gmail.com>
wrote:
On 25 October 2012 23:03, Figue <ffigue@gmail.com> wrote:
I've a similar issue like you with Deluge. A post that describes what I see in my /var/log: https://bbs.archlinux.org/viewtopic.php?id=123807
|[...] TCP: Possible SYN flooding on port 53126. Dropping request| [...]
I don't have any messages like that on my logs.
A workaround in this case it's disabling SYN flood protection in the
kernel,
adding to /etc/sysctl.conf net.ipv4.tcp_syncookies=0
That doesn't help. I'm starting to think this is ISP related.
Universities networks often block torrent protocol on the proxy level. Also recently (last 2 years) with all that fuzz on torrents and piracy, ISPs usually sniff package traffic and throttle torrents also. Alternative ways have been proposed, search if your ISP is blocking the torrents and what you could do to work around it.
-- Caution: breathing may be hazardous to your health.
#include <stdio.h> int main(){printf("%s","\x4c\x65\x6f\x6e\x69\x64\x61\x73");}
I'll have to ask to my ISP and to the university about it, as it does not happen on all trackers. Thank you all for your help and sorry for the noise
participants (4)
-
Alexandre Ferrando
-
Figue
-
Gaetan Bisson
-
Leonidas Spyropoulos