Re: AS3549 Level3/GBLX carrying routing for 10.0.0.0/8
Perhaps we should all take a moment and review RFC 5735, 6598, 6890, and 5156 and implement filtering in the appropriate places and help make the Internet a safer place to play. Think of the children! ...heh --chip On Mon, Jul 22, 2013 at 3:44 PM, Christopher Morrow wrote: > On Mon, Jul 22, 2013 at 3:36 PM, Siegel, David > wrote: > > This should now be fixed. > > > > As a general matter of policy, we do filter out 10/8, but somehow the > filter list for a customer was empty which then defaults to an implicit > accept. We're in the process of improving our config audits to catch this > in the future. > > > > what happens if they register a route object for 10/8? :) > > > Dave > > > > > > > > -Original Message- > > From: Larry Sheldon [mailto:larryshel...@cox.net] > > Sent: Saturday, July 20, 2013 10:31 PM > > To: nanog@nanog.org > > Subject: Re: AS3549 Level3/GBLX carrying routing for 10.0.0.0/8 > > > > On 7/20/2013 11:26 PM, Yang Yu wrote: > >> It appears AS3549 is announcing 10.0.0.0/8. I noticed it from an > >> AS3549 customer. > > > > I wonder why people don't drop any update that contains stuff like RFC > > 1918 space. > > -- > > Requiescas in pace o email Two identifying characteristics > > of System Administrators: > > Ex turpi causa non oritur actio Infallibility, and the ability to > > learn from their mistakes. > >(Adapted from Stephen Pinker) > > > > > > -- Just my $.02, your mileage may vary, batteries not included, etc
Re: AS3549 Level3/GBLX carrying routing for 10.0.0.0/8
On Mon, Jul 22, 2013 at 3:36 PM, Siegel, David wrote: > This should now be fixed. > > As a general matter of policy, we do filter out 10/8, but somehow the filter > list for a customer was empty which then defaults to an implicit accept. > We're in the process of improving our config audits to catch this in the > future. > what happens if they register a route object for 10/8? :) > Dave > > > > -Original Message- > From: Larry Sheldon [mailto:larryshel...@cox.net] > Sent: Saturday, July 20, 2013 10:31 PM > To: nanog@nanog.org > Subject: Re: AS3549 Level3/GBLX carrying routing for 10.0.0.0/8 > > On 7/20/2013 11:26 PM, Yang Yu wrote: >> It appears AS3549 is announcing 10.0.0.0/8. I noticed it from an >> AS3549 customer. > > I wonder why people don't drop any update that contains stuff like RFC > 1918 space. > -- > Requiescas in pace o email Two identifying characteristics > of System Administrators: > Ex turpi causa non oritur actio Infallibility, and the ability to > learn from their mistakes. >(Adapted from Stephen Pinker) > >
RE: AS3549 Level3/GBLX carrying routing for 10.0.0.0/8
This should now be fixed. As a general matter of policy, we do filter out 10/8, but somehow the filter list for a customer was empty which then defaults to an implicit accept. We're in the process of improving our config audits to catch this in the future. Dave -Original Message- From: Larry Sheldon [mailto:larryshel...@cox.net] Sent: Saturday, July 20, 2013 10:31 PM To: nanog@nanog.org Subject: Re: AS3549 Level3/GBLX carrying routing for 10.0.0.0/8 On 7/20/2013 11:26 PM, Yang Yu wrote: > It appears AS3549 is announcing 10.0.0.0/8. I noticed it from an > AS3549 customer. I wonder why people don't drop any update that contains stuff like RFC 1918 space. -- Requiescas in pace o email Two identifying characteristics of System Administrators: Ex turpi causa non oritur actio Infallibility, and the ability to learn from their mistakes. (Adapted from Stephen Pinker)
Re: AS3549 Level3/GBLX carrying routing for 10.0.0.0/8
On 7/20/2013 11:26 PM, Yang Yu wrote: It appears AS3549 is announcing 10.0.0.0/8. I noticed it from an AS3549 customer. I wonder why people don't drop any update that contains stuff like RFC 1918 space. -- Requiescas in pace o email Two identifying characteristics of System Administrators: Ex turpi causa non oritur actio Infallibility, and the ability to learn from their mistakes. (Adapted from Stephen Pinker)
AS3549 Level3/GBLX carrying routing for 10.0.0.0/8
It appears AS3549 is announcing 10.0.0.0/8. I noticed it from an AS3549 customer. >From GBLX looking glass, ATL1 traceroute Protocol [ip]: ip Target IP address: 10.0.0.1 Source address: Numeric display [n]: n Timeout in seconds [3]: 1 Probe count [3]: 2 Minimum Time to Live [1]: 1 Maximum Time to Live [30]: 30 Port Number [33434]: Loose, Strict, Record, Timestamp, Verbose[none]: Type escape sequence to abort. Tracing the route to 10.0.0.1 VRF info: (vrf in name/id, vrf out name/id) 1 te3-1-10G.par9.CTA1.GRU.gblx.net (67.16.142.26) 120 msec 124 msec 2 122.5.125.189.static.impsat.net.br (189.125.5.122) 120 msec 120 msec 3 10.0.0.1 [AS 262487] 124 msec 120 msec Apparently the customer didn't have proper inbound filter.. Reply from 10.0.0.1: bytes=32 time=132ms TTL=61
