|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: 168.0.0.0/6
This has been mentioned on nanog maillist before, it appears several months after notification swisscom still has not fixed this problem (when similar leak came from he, I think they fixed it in 48 hours!). Here are pointers to previous thread: http://www.merit.edu/mailinglist/mailarchives/old_archive/2003-11/msg00626.html http://www.merit.edu/mailinglist/mailarchives/old_archive/2003-11/msg00636.html On Wed, 25 Feb 2004, Randy Bush wrote: > >> route-views.oregon-ix.net>sh ip bgp 169.223.0.0 > >> BGP routing table entry for 168.0.0.0/6, version 7688303 > >> Paths: (1 available, best #1, table Default-IP-Routing-Table) > >> Not advertised to any peer > >> 3277 13062 20485 20485 20485 8437 3303 > >> 194.85.4.249 from 194.85.4.249 (194.85.4.249) > >> Origin IGP, localpref 100, valid, external, best > > > > *> 24.0.0.0 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 60.0.0.0/7 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 62.0.0.0 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 63.0.0.0 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 64.0.0.0/6 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 68.0.0.0/7 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 70.0.0.0 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 80.0.0.0/6 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 84.0.0.0 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 128.0.0.0/3 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 160.0.0.0/5 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 168.0.0.0/6 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 199.0.0.0/8 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 200.0.0.0/7 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 202.0.0.0/7 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 204.0.0.0/6 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 208.0.0.0/7 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 210.0.0.0/7 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 212.0.0.0/7 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 216.0.0.0/8 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 217.0.0.0/8 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 218.0.0.0/7 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 220.0.0.0/7 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > *> 222.0.0.0/8 194.85.4.249 0 3277 13062 20485 20485 20485 8437 3303 i > > this seems to cause some strangeness when one's block is having various > announcement problems and falls within swisscom's imperialistic reach. is > cousin george doing their routing policy? :-) > > randy >
|