[174985] in North American Network Operators' Group
Re: Weird Issues within L3
daemon@ATHENA.MIT.EDU (Blair Trosper)
Tue Oct 7 17:19:38 2014
X-Original-To: nanog@nanog.org
In-Reply-To: <dc30400e121242c0ae3147249eac7e9d@flhsi.com>
Date: Tue, 7 Oct 2014 16:19:30 -0500
From: Blair Trosper <blair.trosper@gmail.com>
To: nick@flhsi.com
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Not to mention known bugs with how traffic is routed in large system like
Google...because of any/multicast and all. (I hear it's a known bug
internally.)
I personally love the Level 3 public DNS servers, but they do carry some
quirks with them, as all things in life do.
On Tue, Oct 7, 2014 at 3:51 PM, Nick Olsen <nick@flhsi.com> wrote:
> The 4.2.2.x machines are known to have some pretty heavy handed ICMP rate
> limits.
>
> I'd suggest trying to hit anything on level3 but those...
>
> Nick Olsen
> Network Operations (855) FLSPEED x106
>
>
> ----------------------------------------
> From: "Khurram Khan" <kkhan@brokenflea.net>
> Sent: Tuesday, October 07, 2014 4:48 PM
> To: "nanog@nanog.org" <nanog@nanog.org>
> Subject: Weird Issues within L3
> Hi Group,
>
> We have a couple of circuits , internet facing with Level 3 and from
> our edge in San Diego, seeing some packet loss when trying a ping to
> 4.2.2.4, sourcing from 63.214.184.3. anyone seeing a similar issue ?
>
> Packet sent with a source address of 63.214.184.3
> !.!!!.!!!!!!!!!!!!!...!!!..!!!!!!.!!.!!!!!!.!..!!.!!.!!!!!!!!!!!!!!!!!
> !!!!!!!!!.!!.!!!..!!!!!.!!!!.!
> Success rate is 80 percent (80/100), round-trip min/avg/max = 12/13/16 ms
>
>
>
