Global routing problem with 178.0.0.0/8 - Update your IANA filter lists
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? Cheers! -- Sven Wiese General Director I.C.S. "Trabia-Network" S.R.L. [t] +373 (22) 844-844 [e] s.wiese@trabia.net [i] www.trabia.net Privileged/Confidential Information may be contained in this message. If you are not in the addresses indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such a case, you should destroy this message and kindly notify the sender by reply e-mail.
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.
Hello, this is a well known problem which regularly occures when new IP space gets allocated to the RIRs. Even though RIPE typically has a delay between getting those IPs allocated by IANA and deligating it to it's members and those IP blocks are initially announced by RIPE (typically as /8), there are always networks that do not update the bogon filters routinely. There are only two solutions to this problem: Try to contact those networks in order to get their filters updated or simply wait...... Best regards, Franz Georg Köhler Am 08.04.10 20:00, schrieb Michal Buchtik:
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.
On 8 Apr 2010, at 17:23, Sven Wiese [Trabia-Network] wrote:
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".
Yes, this happens and it's very sad. When we are supporting a network in 'new' space, and an outdated bogon list is hurting the availability of services hosted in the new space, we encourage end users connected to the ISP with broken config, to complain directly to their ISP. Some ISPs tend to listen to their customers more than third parties in the community. The down side to this approach is that the broken ISP don't really learn how to fix the structural problem (swap to dynamic updates of bogons via the Cymru service, or keep up to date with newly allocated /8s), but it does make 'stuff work' for my customer. Since all v4 will be allocated to RIRs and available for assignment in ~500 days, I question the value of filtering the virgin /8s, and tend just to filter the 1918, example, 224/3, and autoconf ranges on kit that I administer now... Andy
participants (4)
-
'Sven Wiese -
Andy Davidson -
Franz Georg Köhler -
Michal Buchtik