[RndTbl] Shaw packet loss

Sean Walberg sean at ertw.com
Tue Oct 19 11:28:39 CDT 2010


With all the frapping ARP requests that are broadcast (and therefore being
sent out by the head end) I'm not surprised the control plane is swamped :P

Sean

On Tue, Oct 19, 2010 at 11:17 AM, Adam Thompson <athompso at athompso.net>wrote:

> 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.
>
> *sigh*  I can't believe I'm defending Shaw...
>
> -Adam
>
> -----Original Message-----
> From: John Lange <john at johnlange.ca>
> Sender: roundtable-bounces at muug.mb.ca
> Date: Tue, 19 Oct 2010 11:14:16
> To: Continuation of Round Table discussion<roundtable at muug.mb.ca>
> Reply-To: Continuation of Round Table discussion <roundtable at muug.mb.ca>
> Subject: Re: [RndTbl] Shaw packet loss
>
> Just for reference; I use mtr for testing this.
>
> Here is the command line. As you can see, I've set a very aggressive
> packet rate (20/second).
>
> # mtr -r -w -c 500 -n -i 0.05 www.google.ca
>
> I actually stick it in a loop so I can keep it running and see periodic
> results:
>
> # while true ; do date ; mtr -r -w -c 500 -n -i 0.05 www.google.ca ; done
>
> When I see loss, it's always at the first hop yet it doesn't seem to
> matter which gateway it is. These are all Shaw business customers so
> may not be affecting residential.
>
> John
>
> On Tue, Oct 19, 2010 at 10:57 AM, Mike Pfaiffer <high.res.mike at gmail.com>
> wrote:
> > On 10-10-19 10:39 AM, Sean Walberg wrote:
> >> On Tue, Oct 19, 2010 at 10:36 AM, Mike Pfaiffer<high.res.mike at gmail.com
> >wrote:
> >>
> >>
> >>>         Then there is their policy of slowing down the entire
> connection if
> >>> they 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 at muug.mb.ca
> > http://www.muug.mb.ca/mailman/listinfo/roundtable
> >
>
>
>
> --
> John Lange
> www.johnlange.ca
>
> _______________________________________________
> Roundtable mailing list
> Roundtable at muug.mb.ca
> http://www.muug.mb.ca/mailman/listinfo/roundtable
>
>
> _______________________________________________
> Roundtable mailing list
> Roundtable at muug.mb.ca
> http://www.muug.mb.ca/mailman/listinfo/roundtable
>



-- 
Sean Walberg <sean at ertw.com>    http://ertw.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.muug.mb.ca/pipermail/roundtable/attachments/20101019/8780716c/attachment.html 


More information about the Roundtable mailing list