L3 outage

2007-02-26 Thread David Lesher
I'm told {by atlantech.net} that L3 is wounded in the east-central region; i.e. DC-NYC at least... -- A host is a host from coast to [EMAIL PROTECTED] & no one will talk to a host that's close[v].(301) 56-LINUX Unless the host (that isn't close).pob 1433 is busy

Re: 96.2.0.0/16 Bogons

2007-02-26 Thread Randy Bush
> i know its all the rage to post/shame the offending parties (those > whois filtering policies don't reflect our own) bull we are trying to validate experimental results. sorry if that offends you or you do your research result validation differently. randy

Re: 96.2.0.0/16 Bogons

2007-02-26 Thread bmanning
i know its all the rage to post/shame the offending parties (those whois filtering policies don't reflect our own) - BUT - how hard would it be for you perl jocks to publish the ASNs of the "good guys" --bill

RE: 96.2.0.0/16 Bogons

2007-02-26 Thread Frank Bulk
Randy: Sorry, our upstream provider's ASN is not listed in that filter-candidates.txt document. Kind regards, Frank -Original Message- From: Randy Bush [mailto:[EMAIL PROTECTED] Sent: Monday, February 26, 2007 4:34 PM To: Frank Bulk Cc: nanog@merit.edu Subject: RE: 96.2.0.0/16 Bogons

RE: 96.2.0.0/16 Bogons

2007-02-26 Thread Randy Bush
> 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, could your links be in

Re: 96.2.0.0/16 Bogons

2007-02-26 Thread Randy Bush
> 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

RE: 96.2.0.0/16 Bogons

2007-02-26 Thread Frank Bulk
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 __

RE: 96.2.0.0/16 Bogons

2007-02-26 Thread Eric Ortega
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: nanog@merit.e

Re: 96.2.0.0/16 Bogons

2007-02-26 Thread James Blessing
-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

96.2.0.0/16 Bogons

2007-02-26 Thread Eric Ortega
> 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

Re: botnets: web servers, end-systems and Vint Cerf

2007-02-26 Thread Eric Gauthier
Gadi, > Can you elaborate a bit on what universities have done which would be > relevant to service providers here? Generally, we've found that most end users don't even know that their systems are infected - be it with spyware, bots, etc - and are happy when we can help them clear things up as