North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

RE: 96.2.0.0/16 Bogons

  • From: Eric Ortega
  • Date: Wed Feb 28 17:05:56 2007

I'd like to thank the group for the responses and help with this issue. I
find it ironic that Randy's study actually uses 96 space. 

Thanks again!

Eric

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Eric
Ortega
Sent: Monday, February 26, 2007 12:17 PM
To: [email protected]
Cc: 'James Blessing'
Subject: RE: 96.2.0.0/16 Bogons



After I sent that mail I realized that I didn't give enough information.
96.2.0.1 is pingable from the net.

Thank you all for your quick response!

-----Original Message-----
From: James Blessing [mailto:[email protected]] 
Sent: Monday, February 26, 2007 11:28 AM
To: Eric Ortega
Cc: [email protected]
Subject: Re: 96.2.0.0/16 Bogons


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Eric Ortega wrote:

> I am a network engineer for Midcontinent Communications We are an ISP
> in the American Midwest. Recently, we were allocated a new network
> assignment: 96.2.0.0/16. We've been having major issues with sites 
> still blocking this network. I normally wouldn't blanket post to the 
> group, but I'm looking to hit as many direct network 
> engineers/operators as possible.  Would it be possible to have people 
> do a quick check on their inbound filters?

Pingable IP address in that network please :)

- --
COO
Entanet International
T: 0870 770 9580
http://www.enta.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF4xiRR+KszLBLUT8RAnR/AJ43MzH5PUaTflUsPU95MUp4iuZolQCfcJAZ
Y6j4ipQBBseS/VhdvT8ry6c=
=t+y8
-----END PGP SIGNATURE-----