Using Connection Limits to defeat torrents
Posted: Wed Jul 04, 2012 10:41 am
I got a NetEqualizer yesterday and ordered a Netgear 3700 today which will be running Gargoyle 1.5.4. I corresponded with pbix about comparing these two Active Traffic Control devices. I'll do that as soon as I actually start using Gargoyle. For now, having a great time understanding the NetEqualizer.
And since I wrote just hours ago I have begun testing Connection Limits on the NetEqualizer and have found them surprisingly effective in blocking P2P.
A simple limit of 40 (20 up, 20 down) allows normal activities.
Pre-uTorrent
-------------------
I just checked, this machine has 7 open connections, with two dozen tabs open and a lot of other items active. Baseline upload and download are both single digits, a few kilobit. Latency to my ISP gateway is at 15ms. By the way, the NetLimiter app is a great way to see connections and their speeds. That and BitMeter.
Open uTorrent
------------------------
Opening uTorrent takes this machine to hundreds of connections. This happens even if I am not downloading; it *always* seeds. Upload is always maxed out to the max upload allowed by my ISP. That also quickly takes latency to my ISP gateway from a normal value of 15 to 2000ms or higher. Pinging my ISP gateway now takes over two seconds - this is a problem.
POOF !
All I did was open a torrent application and the whole network is trashed. Even if I'm not downloading. Even with a $1,400 NetEqualizer running. That torrent application is a serious destructive force. And all it takes is one person on the network to run it or iTunes or other P2P to instantly trash the entire network. Now everything is slow.
But, NetEqualizer also lets me set Connection Limits by IP and IP range. And to be fair, it is part of the initial setup process in the Quickstart guide. So I used a recommended value of 40 (20 up/20 down) and set it for 192.168.254.124, my current IP on this machine.
Open uTorrent, but this time with Connection Limits
-------------------------------------------------------------------------
Now let's open uTorrent again.
And let's watch NetLimiter to see how many processes are spawning, each trying to open a connection. Hmmm the scroll box under the uTorrent category just went from long rectangle to tiny square. There are 21 processes per page, and I can page down more than 40 times so it's somewhere north of 800. Those are new processes spawned by uTorrent, all trying to open up new connections and *choke this network*.
But now very few of these new processes are making lasting connections.
How many of these connections succeed? Well, looking at Active Connections as seen by NetEqualizer, this machine now has 35, up from 7 before opening uTorrent.
And, looking at Bitmeter for my bandwidth utilization for this machine, it's 20some kilobit upload and nine kilobit download. That's pretty close to single digits - nowhere near maxed out.
Latency (pingtime) to my ISP gateway is now around 60-100 ms for everybody else on my network. On my machine I get a lot of ping timeouts because the machine is crawling the walls desperately trying to initiate those 800 uTorrent connections.
And looking at uTorrent itself, there are Zero active torrents.
It just sits there and does no uploading or downloading. Number of torrents in Active status stays at zero. It's like it's broken.
"What happened to uTorrent? It's not working?"
"Yep, you got that right! That's because it just had its legs sawed off by setting Connection Limits. That's why you can still watch your YouTube..."
What's more, as long as it is running and still trying to exceed its connection limits, I can't open any new connections, like a new Google search. If I shut down uTorrent, everything works as normal.
Two hours ago I wasn't sure if Connection Limits would tame the torrent issue. If you fret about torrent control, take comfort in these findings. Setting connection limits of 40 on this machine with the NetEqualizer completely crippled uTorrent. You could do it network-wide by just setting a network range. And, the browser can't open up new things until uTorrent has been definitively quit. People remember that sort of thing.
Quite impressed - using connection limits to control P2P definitely works ! I don't even know if Gargoyle has per-user Connection Limits; I bet it does. I will definitely be using them on whatever routing solution I use.
Now I have to find something new to worry about because Connection Limits certainly crush the torrent menace. It took a few hours of testing to realize how well it works. What a powerful new tool in keeping your public networks running smoothly.
Did you ever worry about that one person in 20 who fires up torrents on every network they log onto? Oh *you* are that guy?
Well just set connection limits on your network and find something else to worry about.
And since I wrote just hours ago I have begun testing Connection Limits on the NetEqualizer and have found them surprisingly effective in blocking P2P.
A simple limit of 40 (20 up, 20 down) allows normal activities.
Pre-uTorrent
-------------------
I just checked, this machine has 7 open connections, with two dozen tabs open and a lot of other items active. Baseline upload and download are both single digits, a few kilobit. Latency to my ISP gateway is at 15ms. By the way, the NetLimiter app is a great way to see connections and their speeds. That and BitMeter.
Open uTorrent
------------------------
Opening uTorrent takes this machine to hundreds of connections. This happens even if I am not downloading; it *always* seeds. Upload is always maxed out to the max upload allowed by my ISP. That also quickly takes latency to my ISP gateway from a normal value of 15 to 2000ms or higher. Pinging my ISP gateway now takes over two seconds - this is a problem.
POOF !
All I did was open a torrent application and the whole network is trashed. Even if I'm not downloading. Even with a $1,400 NetEqualizer running. That torrent application is a serious destructive force. And all it takes is one person on the network to run it or iTunes or other P2P to instantly trash the entire network. Now everything is slow.
But, NetEqualizer also lets me set Connection Limits by IP and IP range. And to be fair, it is part of the initial setup process in the Quickstart guide. So I used a recommended value of 40 (20 up/20 down) and set it for 192.168.254.124, my current IP on this machine.
Open uTorrent, but this time with Connection Limits
-------------------------------------------------------------------------
Now let's open uTorrent again.
And let's watch NetLimiter to see how many processes are spawning, each trying to open a connection. Hmmm the scroll box under the uTorrent category just went from long rectangle to tiny square. There are 21 processes per page, and I can page down more than 40 times so it's somewhere north of 800. Those are new processes spawned by uTorrent, all trying to open up new connections and *choke this network*.
But now very few of these new processes are making lasting connections.
How many of these connections succeed? Well, looking at Active Connections as seen by NetEqualizer, this machine now has 35, up from 7 before opening uTorrent.
And, looking at Bitmeter for my bandwidth utilization for this machine, it's 20some kilobit upload and nine kilobit download. That's pretty close to single digits - nowhere near maxed out.
Latency (pingtime) to my ISP gateway is now around 60-100 ms for everybody else on my network. On my machine I get a lot of ping timeouts because the machine is crawling the walls desperately trying to initiate those 800 uTorrent connections.
And looking at uTorrent itself, there are Zero active torrents.
It just sits there and does no uploading or downloading. Number of torrents in Active status stays at zero. It's like it's broken.
"What happened to uTorrent? It's not working?"
"Yep, you got that right! That's because it just had its legs sawed off by setting Connection Limits. That's why you can still watch your YouTube..."
What's more, as long as it is running and still trying to exceed its connection limits, I can't open any new connections, like a new Google search. If I shut down uTorrent, everything works as normal.
Two hours ago I wasn't sure if Connection Limits would tame the torrent issue. If you fret about torrent control, take comfort in these findings. Setting connection limits of 40 on this machine with the NetEqualizer completely crippled uTorrent. You could do it network-wide by just setting a network range. And, the browser can't open up new things until uTorrent has been definitively quit. People remember that sort of thing.
Quite impressed - using connection limits to control P2P definitely works ! I don't even know if Gargoyle has per-user Connection Limits; I bet it does. I will definitely be using them on whatever routing solution I use.
Now I have to find something new to worry about because Connection Limits certainly crush the torrent menace. It took a few hours of testing to realize how well it works. What a powerful new tool in keeping your public networks running smoothly.
Did you ever worry about that one person in 20 who fires up torrents on every network they log onto? Oh *you* are that guy?

Well just set connection limits on your network and find something else to worry about.