Oddities in a bad route announcement
M. David Leonard
mdl at equinox.shaysnet.com
Sat May 29 13:35:09 UTC 1999
Sean-
It looks OK from here right now:
traceroute to infoserver.fcc.gov (192.104.54.3), 30 hops max, 40 byte packets
1 ShaysNet-gw.shaysnet.com (199.170.68.2) 3 ms 3 ms 3 ms
2 Loopback0.GW2.BOS1.Alter.Net (137.39.2.208) 9 ms 9 ms 9 ms
3 124.ATM2-0.XR1.BOS1.ALTER.NET (146.188.176.242) 8 ms 9 ms 8 ms
4 291.ATM2-0.TR1.NYC1.ALTER.NET (146.188.179.90) 14 ms 13 ms 14 ms
5 104.ATM7-0.TR1.DCA8.ALTER.NET (146.188.138.117) 21 ms 20 ms 20 ms
6 152.63.32.165 (152.63.32.165) 20 ms 19 ms 20 ms
7 195.ATM9-0-0.GW2.DCA3.ALTER.NET (146.188.163.185) 21 ms 21 ms 24 ms
8 fcc.gov-gw.customer.alter.net (157.130.39.150) 21 ms 22 ms 22 ms
9 infoserver.fcc.gov (192.104.54.3) 26 ms * 24 ms
But (IIRC) Warwick Online hosed UUNet a few months back by
injecting BGP bogons into their backbone. It appeared to be a router
misconfiguration at the time. Maybe this was just another typo (JAT).
Regards,
David Leonard
ShaysNet
More information about the NANOG
mailing list