Mike, that sounds more like your gateway router running out of CPU cycles than Shaw doing traffic management. I work with an ISP: doing the sort of thing you're describing *is* possible, but insanely difficult and expensive, especially on Shaw's scale. I have a 2GHz router, it should handle it - I can test later this week. -Adam
-----Original Message----- From: Mike Pfaiffer high.res.mike@gmail.com Sender: roundtable-bounces@muug.mb.ca Date: Tue, 19 Oct 2010 10:57:39 To: Continuation of Round Table discussionroundtable@muug.mb.ca Reply-To: Continuation of Round Table discussion roundtable@muug.mb.ca Subject: Re: [RndTbl] Shaw packet loss
On 10-10-19 10:39 AM, Sean Walberg wrote:
On Tue, Oct 19, 2010 at 10:36 AM, Mike Pfaifferhigh.res.mike@gmail.comwrote:
Then there is their policy of slowing down the entire connection ifthey determine someone is using bittorrent on a LAN (even if the user caps the up and down speeds)
Do you have a source for this? Are you sure it's not because you're starving out your upstream and therefore not able to get ACKs out?
Sean
Give it a try. Grab a movie or something. Use a bittorrent client capable of capping the up and down speed. Ktorrent can do this. See what you can get for both up and down uncapped. Then try running say Firefox and look at its performance. Stop the bittorrent transfer and look at Firefox again in a few minutes. Set up a cap in bittorrent say 10K on both the up and down (bear in mind this is supposed to be a multi-megabit connection). Restart your bittorrent and see what happens with Firefox. You'll notice the bittorrent will transfer to what ever maximum you set while other programs will barely function on the internet. Local transfers on the LAN are fine though.
Later Mike
_______________________________________________ Roundtable mailing list Roundtable@muug.mb.ca http://www.muug.mb.ca/mailman/listinfo/roundtable