You mean <a href="http://www.shaw.ca/en-ca/AboutShaw/TermsofUse/AcceptableUsePolicyInternet.htm#traffic">http://www.shaw.ca/en-ca/AboutShaw/TermsofUse/AcceptableUsePolicyInternet.htm#traffic</a><div><br></div><div><a href="http://www.shaw.ca/en-ca/AboutShaw/TermsofUse/AcceptableUsePolicyInternet.htm#traffic"></a>? :P</div>
<div><br></div><div>Sean<br><br><div class="gmail_quote">On Tue, Oct 19, 2010 at 11:18 AM, John Lange <span dir="ltr"><<a href="mailto:john@johnlange.ca">john@johnlange.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Just a side note on the shaping; the CRTC now requires that ISPs<br>
disclose their traffic shaping policy. You could request that Shaw<br>
give you that information and when they don't, take the complaint to<br>
the CRTC. Of course it will be a wast of time but I'd actually like<br>
someone to go through the process just to see if the CRTC ruling has<br>
had any effect.<br>
<br>
I just have not had any time to do this myself.<br>
<font color="#888888"><br>
John<br>
</font><div><div></div><div class="h5"><br>
On Tue, Oct 19, 2010 at 10:57 AM, Mike Pfaiffer <<a href="mailto:high.res.mike@gmail.com">high.res.mike@gmail.com</a>> wrote:<br>
> On 10-10-19 10:39 AM, Sean Walberg wrote:<br>
>> On Tue, Oct 19, 2010 at 10:36 AM, Mike Pfaiffer<<a href="mailto:high.res.mike@gmail.com">high.res.mike@gmail.com</a>>wrote:<br>
>><br>
>><br>
>>> Then there is their policy of slowing down the entire connection if<br>
>>> they determine someone is using bittorrent on a LAN (even if the user<br>
>>> caps the up and down speeds)<br>
>><br>
>><br>
>> Do you have a source for this? Are you sure it's not because you're starving<br>
>> out your upstream and therefore not able to get ACKs out?<br>
>><br>
>> Sean<br>
>><br>
><br>
> Give it a try. Grab a movie or something. Use a bittorrent client<br>
> capable of capping the up and down speed. Ktorrent can do this. See what<br>
> you can get for both up and down uncapped. Then try running say Firefox<br>
> and look at its performance. Stop the bittorrent transfer and look at<br>
> Firefox again in a few minutes. Set up a cap in bittorrent say 10K on<br>
> both the up and down (bear in mind this is supposed to be a<br>
> multi-megabit connection). Restart your bittorrent and see what happens<br>
> with Firefox. You'll notice the bittorrent will transfer to what ever<br>
> maximum you set while other programs will barely function on the<br>
> internet. Local transfers on the LAN are fine though.<br>
><br>
> Later<br>
> Mike<br>
><br>
> _______________________________________________<br>
> Roundtable mailing list<br>
> <a href="mailto:Roundtable@muug.mb.ca">Roundtable@muug.mb.ca</a><br>
> <a href="http://www.muug.mb.ca/mailman/listinfo/roundtable" target="_blank">http://www.muug.mb.ca/mailman/listinfo/roundtable</a><br>
><br>
<br>
<br>
<br>
</div></div><div class="im">--<br>
John Lange<br>
<a href="http://www.johnlange.ca" target="_blank">www.johnlange.ca</a><br>
<br>
_______________________________________________<br>
</div><div><div></div><div class="h5">Roundtable mailing list<br>
<a href="mailto:Roundtable@muug.mb.ca">Roundtable@muug.mb.ca</a><br>
<a href="http://www.muug.mb.ca/mailman/listinfo/roundtable" target="_blank">http://www.muug.mb.ca/mailman/listinfo/roundtable</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Sean Walberg <<a href="mailto:sean@ertw.com">sean@ertw.com</a>> <a href="http://ertw.com/">http://ertw.com/</a><br>
</div>