North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Operational Issues with 188.8.131.52/8...
Thanks for the reply, James. I wish I could tell you the answer. We see traffic passing through some of the routers (transit), but on each network, or their downstreams there seem to be different devices filtering. Sometimes it is a border or peering router. In other cases, it has been access devices, such as firewalls. One we resolved this morning (with some help from the good folks at ARIN) was a downstream provider from one of these transit providers that was filtering in their devices as well. I am just trying to raise general awareness that the 184.108.40.206/8 block is assigned and out there in use, and to get people to re-examine their filters, access lists, etc. You help and response is appreciated. Sincerely, Todd A. Blank 614.207.5853 -----Original Message----- From: Feger, James [mailto:email@example.com] Sent: Monday, December 02, 2002 1:35 PM To: Todd A. Blank Subject: Re: Operational Issues with 220.127.116.11/8... When you say 'Networks involved' do you mean those providers are blocking the traffic, or you see these networks in the transit? Thanks, James On Mon, 2 Dec 2002, Todd A. Blank wrote: > > To all concerned: > > We have been assigned a CIDR of 18.104.22.168/19. > > We have had numerous problems getting traffic through to various destinations. > > We are finding that many routers are still filtering 22.214.171.124/8. > > This block used to be restricted, but was assigned by IANA to ARIN in August of 2002. > > If anyone is still filtering this block in their routers, please remove the filters! > > Here are some of the destinations that are not reachable if your source is anywhere in the 126.96.36.199/8 CIDR: > > www.cplink2.com > www.ocas.com > www.indofilms.com > www.lavalife.com > > > Some of the Networks involved are Cable and Wireless, Allegiance Internet and AT&T. > > Thank you, > > Todd A. Blank > IPOutlet LLC > 614.207.5853 >