First off, i'd like to start by saying that i'm completely aware of the affects P2P downloading can have on a network when the proper settings are not configured. However, I believe to have them set up the way they should be as it has worked perfectly fine for me in the past of the stock build of Tomato.
For some reason and i'm not quite sure why, downloading torrents kills my bandwidth even with QoS set up. All my QoS classifications are left to default and my bandwidth is set accordingly. I would go and list all my QoS bandwidth settings but I think the point is moot because this issue does not occur on the original Tomato 1.28 ND build with the same exact settings for everything.
For the WL-520GU I used K26USB-1.28.9048MIPSR1-beta18-Lite.
I use uTorrent on a laptop with Windows 7. In uTorrent I have it set up to use a max upload 50 kBs. My max upload bandwidth from my provider is 1mbs. In my QoS settings i've even set this under at 800kBs because I know i'm not actually going to be getting the full 1mbs from my provider anyways. I've done a similar setup for my download bandwidth.
My torrent port falls within the port range of the default "Bulk traffic" classification of Tomato's QoS. So it should be receiving the least priority.
Within seconds of starting my torrents up using Tomato USB i'm unable to browse to any page in my browser. Everything times out. The router is not locked up though because the torrents are still going strong.
I've flashed back and forth between K26USB-1.28.9048MIPSR1-beta18-Lite and Tomato-1.28-ND several times clearing the NVRAM between each change and configuring my settings back manually each time. The only settings I adjust from the stock settings are the QoS Basic Settings and of course my Wireless SSID etc… I don't change any advanced settings of any kind.
Everytime I do this, everything works perfect in the original Tomato firmware and fails in the USB mod version.
The only thing I have not tried is the K24 build of the USB mod.
Another issue I've noticed that leads me to believe that it may not be bandwidth related though is that when this issue occurs, it can't even bring up 192.168.1.1 until I pause the torrents. This should still be able to come up regardless of bandwidth consumption right?
Could this mean that somehow the router itself is getting overloaded? I've limited the connections in uTorrent itself to only 500.
And once again. What throws me off the most is that it works perfectly fine in Tomato 1.28 ND build with all the same exact settings.
Sorry if I did nothing more than confuse anyone reading this.