Hi !
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 hmmm... this could be a solution, but from what source does uunet generate this filter-list ? The Ripe-Database contains this route object:
route: 151.189.0.0/16 descr: CALLISTO origin: AS6751 notify: guardian@seicom.net notify: guardian@germany.net mnt-by: AS6751-MNT changed: wh@seicom.net 19980126 source: RIPE
access-list xyz permit 151.189.0.0 255.255.255.0
instead of (the correct one):
access-list xyz permit 151.189.0.0 255.255.0.0
note the difference ?
yes sure... but the question is, why did uunet change their filters within the last days without action from us or our customer ? And the magic is, the rest of 151.189.0.0 (e.g 151.189.10.0) is seen via 151.189.0.0/16...
It's probably time for them to call the uunet support to fix this.
great !, 2 Tickets are already open, and no response from uunet. A company who is about to control 60% of the us-internet market can manipulate a lot of things and make a lot of money!. I would say at least 50% of the german internet isps are connected to uunet in Frankfurt. With their wrong announcement, their customers got germany traffic over a internation link and paid for this. Whom did they pay ? right uunet.... i think this wasnt a wanted effect currently but it shows what could happen and who gets money for these mistakes. I dont care this /24 in the us, because from our view it makes no difference, but for the german isps it made a big difference. We corrected it by announcing this /24 at mae-ffm, inxs and de-cix but it cant be right that we have to change our announcement because the world-leading isp has wrong filters. And calling uunet in Frankfurt leads into a 10-minute voice claiming your call is important to us... bla bla bla... i think we gonna sent all 30seconds a mail to help@uu.net :-) hopefully their tracking systems beaks down and they are pleased to answer :-) or should we announce 198.6.1.0/24 and route it to /dev/nul... or should we dig a hole and put our uu.net problems there into .... Winfried - frustrated PS: even a mail from the german uu.net people (thanks to them!) is stil without response... -- 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 haug@schwaben.net| 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