[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/10/12 13:13, Alexandre Ferrando wrote:

On 25 October 2012 13:07, Gaetan Bisson 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 Thu, Oct 25, 2012 at 11:31 PM, Alexandre Ferrando wrote:

On 25 October 2012 23:03, Figue 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 int main(){printf("%s","\x4c\x65\x6f\x6e\x69\x64\x61\x73");}