It's not unreasonable to put rate limits on inbound ICMP traffic going to the control plane of the router. But the VoIP loss is unacceptable, I agree.<div><br></div><div>Sean<br><br><div class="gmail_quote">On Tue, Oct 19, 2010 at 12:00 PM, 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;">When the loss occurs it's all the way from hop 1 to the far end.<br>
<br>
They've used the "ICMP is at a lower priority" excuse before. It<br>
doesn't hold much water with me because that is essentially just an<br>
admission that the router is overload and has to start dropping stuff<br>
which would be fine if only ICMP got dropped but the packet loss is<br>
also happening on voice traffic.<br>
<font color="#888888"><br>
John<br>
</font><div><div></div><div class="h5"><br>
<br>
On Tue, Oct 19, 2010 at 11:17 AM, Adam Thompson <<a href="mailto:athompso@athompso.net">athompso@athompso.net</a>> wrote:<br>
> If MTR shows loss at hop 1 but *not* at hop 2, that's just their router ignoring your ICMP packets and doesn't actually indicate packet loss.<br>
><br>
> *sigh* I can't believe I'm defending Shaw...<br>
><br>
> -Adam<br>
><br>
> -----Original Message-----<br>
> From: John Lange <<a href="mailto:john@johnlange.ca">john@johnlange.ca</a>><br>
> Sender: <a href="mailto:roundtable-bounces@muug.mb.ca">roundtable-bounces@muug.mb.ca</a><br>
> Date: Tue, 19 Oct 2010 11:14:16<br>
> To: Continuation of Round Table discussion<<a href="mailto:roundtable@muug.mb.ca">roundtable@muug.mb.ca</a>><br>
> Reply-To: Continuation of Round Table discussion <<a href="mailto:roundtable@muug.mb.ca">roundtable@muug.mb.ca</a>><br>
> Subject: Re: [RndTbl] Shaw packet loss<br>
><br>
> Just for reference; I use mtr for testing this.<br>
><br>
> Here is the command line. As you can see, I've set a very aggressive<br>
> packet rate (20/second).<br>
><br>
> # mtr -r -w -c 500 -n -i 0.05 <a href="http://www.google.ca" target="_blank">www.google.ca</a><br>
><br>
> I actually stick it in a loop so I can keep it running and see periodic results:<br>
><br>
> # while true ; do date ; mtr -r -w -c 500 -n -i 0.05 <a href="http://www.google.ca" target="_blank">www.google.ca</a> ; done<br>
><br>
> When I see loss, it's always at the first hop yet it doesn't seem to<br>
> matter which gateway it is. These are all Shaw business customers so<br>
> may not be affecting residential.<br>
><br>
> John<br>
><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>
> --<br>
> John Lange<br>
> <a href="http://www.johnlange.ca" target="_blank">www.johnlange.ca</a><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>
> 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>
--<br>
John Lange<br>
<a href="http://www.johnlange.ca" target="_blank">www.johnlange.ca</a><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>
</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>