North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Re: Wrong /24 Announcement at UU.net / BGP IOS Bug ?
Hi Vinny! As i am thinking about this, i came to the idea that mostly uu.net applies filters to their downstreams e.g. there are not filtering by as - they filter by access-list what i presume is that they use a access-list xyz permit 22.214.171.124 255.255.255.0 instead of (the correct one): access-list xyz permit 126.96.36.199 255.255.0.0 note the difference ? It's probably time for them to call the uunet support to fix this. Winfried Haug wrote: > Hello.. > > one of our customers (germany.net, AS6751) is announcing us > 188.8.131.52/16. We announce this to our both upstreams > ECRC (AS1273) and Ebone (1755). > > Since a few days a lot of german ISPs ask us, why 184.108.40.206/24 > is routed via UU.net to the USA and then goes back to germany. > > We checked our cisco-routers an finaly i found a Customer of UU.net > with a looking glass: (http://zeus.lyceum.com/cgi-bin/nph-bgp-routes) > > > QUERY: bgp 220.127.116.11 > > FROM: BR1.ATL1.lyceum.net. > > > > BGP routing table entry for 18.104.22.168/24, version 9891827 > > Paths: (1 available, best #1, advertised over IBGP) > > 701 1800 1755 1755 1755 5549 5549 6751 > > 22.214.171.124 from 126.96.36.199 (188.8.131.52) > > Origin IGP, valid, external, best > > ok lets see bacK: > > Sprint (1800) doesnt have this /24 but the /16 as it should be: > > icm-bb4-pen#show ip bgp 184.108.40.206 255.255.255.0 > % Network not in table > icm-bb4-pen# > > the same applies to EBONE (AS1755): > > frankfurt-ebs1>show ip bgp 220.127.116.11 255.255.255.0 > % Network not in table > frankfurt-ebs1> > > an we (AS5549) also dont see any /24 out of 18.104.22.168/16 > > So the question is: why does UU.net announce 22.214.171.124/24 and from > where do they get it. The worse thing is, that all uu.net customers get > this )(&%&$()& /24 from the hub in Frankfurt. The Space > 126.96.36.199 - 188.8.131.52 is visiable at uu.net via 184.108.40.206/16.. > > So what happens here, could this be an ios bug ? > > We didnt touch our configuration towards ebone and they dont play > with their configuration every day :-) > > Any ideas ? hints ? > > Winfried > > PS: for the german isps, we fixed it by announcing only at de-cix the > 220.127.116.11/24 additionally to 18.104.22.168/16 and it works, but > i am still looking for an answer to my questions :-) ? > > -- > > Winfried Haug | seicom.NET & SCHWABEN.DE | Tel. +49 7121 9770- 0 > Laiblinsplatz 12 | Internet+ISDN access & consulting | Fax. +49 7121 9770-19 > 72793 Pfullingen | Access in STGT + RT + TUE + BB + LB | Rack +49 7127 989-X > firstname.lastname@example.org| 150*ISDN (64kb/X.75) / 100 * K56flex | Rack +49 711 9675-X > haug@seicom.NET |SAP-OSS * FTP * TELNET * NETNEWS * IRC | Rack +49 7121 709-X > * 10 MBit DE-CIX * 2 MBit INXS * 5 MBit ecrc/ebone * 2 Mbit Belwue * 2 Mbit WIN