[members-discuss] Global routing problem with 178.0.0.0/8 - Update your IANA filter lists
- Previous message (by thread): [members-discuss] Global routing problem with 178.0.0.0/8 - Update your IANA filter lists
- Next message (by thread): [members-discuss] Global routing problem with 178.0.0.0/8 - Update your IANA filter lists
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michal Buchtik
buchtik at sitkom.cz
Thu Apr 8 20:00:11 CEST 2010
Hi, On 2010/04/08 18:23, 'Sven Wiese [Trabia-Network]' wrote: > Dear Colleagues, > > together with some other LIR's we've discovered there are several > issues with > allocations/assignments made within the 178.0.0.0/8 range. > > Seemingly there are some server/router administrators/companies out > there which > don't regular update their IANA Allocation list. > > We've observed that a lot of networks are unreachable if we use IPs > out of the 178.0.0.0/8 range. > The same observation also made other LIR's we know. > > After contacting these networks (from MD, RO, RU, DE, and other > counties), we figured out > that they all reported they had firewall/filter rules using a IANA > allocation list, and their list > reported 178/8 to be "iana-reserved" or "iana-unallocated". > > The network 178.0.0.0/8 were allocated on January 2009 to the RIPE > NCC, hence > these operators haven't updated their lists for more than 1 year. I guess > the filter was set up once without taking into account that currently > unallocated networks > might get allocated later on. > > This problem concerns everyone at the moment, especially people with > allocations from > 178.0.0.0/8. > > I ask every one of you to check if you use an iana filter list or if > possible, notify your > clients, data centers and so on to check and if necessary update their > lists. > > Are other members in this discussion list maybe observing the same > problem as > we did and our LIR colleagues? > We have same problems with 109/8 (allocated to RIPE NCC on January 2009) When got report about unreachable network/server/(or only one service), we must find and contact administrator of this network/server and ask him to repair firewall. (Sometimes we must tediously explain, that problem is at their side) I wish you luck -- Michal Buchtík SITKOM, s.r.o. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/members-discuss/attachments/20100408/209020dd/attachment.html>
- Previous message (by thread): [members-discuss] Global routing problem with 178.0.0.0/8 - Update your IANA filter lists
- Next message (by thread): [members-discuss] Global routing problem with 178.0.0.0/8 - Update your IANA filter lists
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]