[members-discuss] Global routing problem with 178.0.0.0/8 - Update your IANA filter lists

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