add bittorrent and other p2p protocols (gnutella, etc) with bulk priority.
also assign other services that you need to load fast with anything more than standard (express, premium).
(i.e http & html for web browsing)
Remember assigning bt to bulk alone won't have any significant effect.
You have to set other services that usually slowed down by bt to take precedent over BT itself.
Lets say the traffic WASN'T encrypted. Should the catch all be able to stop it?
Policy is enabled
I have the policy applicable to clients in the range 192.168.1.2->192.168.1.254
Set to Filter
Everyday
24 hours
Catch all P2P checked.
Have I done anything wrong? Do I need to reboot the router or something?
If I can't block it, I don't see how I am going to be able to QOS it?
If I can't block it, I don't see how I am going to be able to QOS it?
Good point
Can't really answer that.
as I don't know what kind of method is used and whether it's the same one when DD-WRT is blocking and/or shaping BT traffic.
But Well.. the QoS works on me. I was able to do a Skyce call without hiccup while my torrent is still active.
If I can't block it, I don't see how I am going to be able to QOS it?
Good point
Can't really answer that.
as I don't know what kind of method is used and whether it's the same one when DD-WRT is blocking and/or shaping BT traffic.
But Well.. the QoS works on me. I was able to do a Skyce call without hiccup while my torrent is still active.
YMMV.
Did you noticed any speed reductions in torrent client while making these calls ?
If I can't block it, I don't see how I am going to be able to QOS it?
Good point
Can't really answer that.
as I don't know what kind of method is used and whether it's the same one when DD-WRT is blocking and/or shaping BT traffic.
But Well.. the QoS works on me. I was able to do a Skyce call without hiccup while my torrent is still active.
YMMV.
Did you noticed any speed reductions in torrent client while making these calls ?
Yes.
Oh and I think I should correct myself, It's not "without" hiccup.
It's just the call experience is much much better than it was before using QoS.
And if there is any kind of voice-spike, the frequency is just more than acceptable, I suppose. _________________ Linksys WRT610nv2 converted to E3000 (AP mode) -> v24 preSP2 Mega build 15962 (Last used build)
^ Currently defecting to Tomato USB 1.28 Shibby Mod
TP-Link TL-WR740N v4 (AP mode) -> v24-sp2 Std build 22118
TP-Link TL-WR841N v8.4 (RB mode) -> v24-sp2 Std build 22102 (last used build)
^ Reverted to Stock 3.13.33 Build 130506 Rel.48660n
If I can't block it, I don't see how I am going to be able to QOS it?
Good point
Can't really answer that.
as I don't know what kind of method is used and whether it's the same one when DD-WRT is blocking and/or shaping BT traffic.
But Well.. the QoS works on me. I was able to do a Skyce call without hiccup while my torrent is still active.
YMMV.
Did you noticed any speed reductions in torrent client while making these calls ?
Yes.
Oh and I think I should correct myself, It's not "without" hiccup.
It's just the call experience is much much better than it was before using QoS.
And if there is any kind of voice-spike, the frequency is just more than acceptable, I suppose.
Did you experienced any call drop-outs, jitter in the voice etc.
I tried to block the keywords you recommended but they didn't stop the five our so torrents I was testing on. Any idea what is wrong? Could it be the sophistication of vuze software?
Any help would be great as the blocking the service method or ports stop our radius server dead for some reason.
I tried to block the keywords you recommended but they didn't stop the five our so torrents I was testing on. Any idea what is wrong? Could it be the sophistication of vuze software?
Any help would be great as the blocking the service method or ports stop our radius server dead for some reason.
Thanks
My flat mate was using vuze and this killed him dead.
Are you setting the Access Policy to enabled and adding a list of clients?
Sounds like you're not setting the policy correctly.
Check the tracker address's in vuze, if the keywords are there then recheck the Access Policy.
Access Policy
Select an empty policy
Status: enable
Policy Name: give it a name
PCs: add a list of clients
Set to Filter
Set everyday
Set 24h
Add keywords. 1 in each empty box
Save and Apply
I know this thread is 3 years old, but I wonder if anyone of you have found an effective way to block torrents using dd-wrt, please?
I see that the 3 word filter has worked for at least one person, and not worked for at least one other - would anyone else care to share their experiences?
