96.2.0.0/16 Bogons

Mon Feb 26 20:07:17 UTC 2007

We found out last Thursday we were blocking that range (our customer base is
across the state line from this Midcon).  Our upstream internet provider,
who manages the BGP side of things, had had their automated Bogon update
process stalled since last fall. =)

Frank

________________________________

From: owner-nanog at merit.edu [mailto:owner-nanog at merit.edu] On Behalf Of Eric
Ortega
Sent: Monday, February 26, 2007 11:26 AM
To: nanog at merit.edu
Subject: 96.2.0.0/16 Bogons

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?

Thanks! 

Eric Ortega 
Midcontinent Communications 
Network Engineer 
605.357.5720 
eric.ortega at midco.net 