North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
RE: Operational Issues with 18.104.22.168/8...
- From: Todd A. Blank
- Date: Mon Dec 02 14:16:13 2002
We feel your pain, Scott. We are just glad that we are able to verify that there are problems with this CIDR other than on our network.
Now to get them resolved. Hopefully this conversation will end up in the proper inboxes to help clean this up.
Does anyone besides me worry that because of the recent cutbacks in this industry that there are orphaned pieces of equipment out there causing some of these problems?
From: Scott Granados [mailto:firstname.lastname@example.org]
Sent: Monday, December 02, 2002 1:52 PM
To: Todd A. Blank
Cc: email@example.com; firstname.lastname@example.org
Subject: Re: Operational Issues with 22.214.171.124/8...
I'd like to second this. We have ran in to problems as well. Usually
this is a great place to get help however we have had very responsive
actions taken by others out there who had filters in place.
On Mon, 2 Dec 2002, Todd A. Blank wrote:
> 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
> 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 126.96.36.199/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.
> Todd A. Blank
> -----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 188.8.131.52/8...
> When you say 'Networks involved' do you mean those providers are
> the traffic, or you see these networks in the transit?
> On Mon, 2 Dec 2002, Todd A. Blank wrote:
> > To all concerned:
> > We have been assigned a CIDR of 184.108.40.206/19.
> > We have had numerous problems getting traffic through to various
> > We are finding that many routers are still filtering 220.127.116.11/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 18.104.22.168/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