[c-nsp] Incorrect ASN in Traceroute

Mark Tinka mark.tinka at seacom.mu
Thu Aug 8 02:39:30 EDT 2013


On Wednesday, August 07, 2013 08:17:46 PM Paul Stewart 
wrote:

> HeheŠ sorry for the flashbacks ;)

My suspicion was that some testing had gone on with AT&T's 
ASN (with or without their knowledge), and one of the coders 
left that in the code by mistake.

> In this particular instance, we had a BGP peer that was
> slipping us a default route.  That route was actually
> making it into the BGP tables locally (but not chosen as
> best route thankfully!).  Guess I need to look at
> tighter filtering again geeshŠ.

Yeah - per-customer prefix lists are annoying (even more 
annoying if you're offering BGP-based RTBH to customers), 
but it's still the best way to stay stafe :-).

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20130808/9e624e94/attachment.sig>


More information about the cisco-nsp mailing list