Page 1 of 2

Not blocking identified torrent traffic

Posted: Sun Apr 07, 2013 7:54 pm
by ferrazrafael
I'm using Gargoyle 1.4.7 on a TP-LINK WR741ND v2. Every thing is working fine except that I make a restriction (whitelist) that allows all traffic but blocks all bittorrent traffic. But in Connection List I can see a lot of bittorrent connection transmitting. This is a bug?

see:
http://postimg.org/image/q8fq3d20x/

Re: Not blocking identified torrent traffic

Posted: Sat Apr 13, 2013 8:08 am
by ispyisail
bittorrent traffic is hard to stop, most is encrypted these days

Re: Not blocking identified torrent traffic

Posted: Sat Apr 13, 2013 7:32 pm
by ferrazrafael
yes, but this traffic is identified it should be blocked. Maybe this is some kind of bug. I need to report it somewhere?

Re: Not blocking identified torrent traffic

Posted: Sat Apr 13, 2013 10:15 pm
by ispyisail
as posted else-ware i recommend trying 1.5.6

Re: Not blocking identified torrent traffic

Posted: Sun Apr 14, 2013 9:03 pm
by ferrazrafael
thanks, I was unsure to test a experimental release. Do you think 1.5.6 is stable enough?

Re: Not blocking identified torrent traffic

Posted: Sun Apr 21, 2013 8:15 pm
by ferrazrafael
I upgraded my wr741nd v2 to gargoyle 1.5.6 and its working fine. But torrent blocking isn't working too.

Re: Not blocking identified torrent traffic

Posted: Mon Apr 22, 2013 2:54 am
by Batublock
I thinks its better you use Quotas for IP that you suspecting using torrent ....

Re: Not blocking identified torrent traffic

Posted: Mon Apr 22, 2013 6:50 pm
by ferrazrafael
yes, but I dont want to punish the guy that uses the internet too much but doesnt cripple the entire network. A normal download is handled quiete well by most routers QoS. But if one of them opens 1000 connections, even if he isnt donwloading at hight rates, this seems to flood the entire network. I didnt test if 1.5.6 handles better torrent than 1.4.7. But if it does, I let you guys know.

Re: Not blocking identified torrent traffic

Posted: Mon Apr 22, 2013 10:57 pm
by Domarius
I am having this same issue. Too many connections (caused by torrenting) kills the network. Not download.

Re: Not blocking identified torrent traffic

Posted: Wed May 15, 2013 2:55 pm
by ferrazrafael
Gargoyle 1.5.6 doesnt handled torrent better. Instead it is dropping wifi signal time to time. So I downgraded to 1.4.7.