nanog mailing list archives

RE: Issue with 208.192.0.0/8 - 208.196.93.0/24?


From: "McBurnett, Jim" <jmcburnett () msmgmt com>
Date: Tue, 11 Mar 2003 10:44:24 -0500


Easy, question..

Sure I could do that, I could run NMAP, Nessus, or any number of probes
to check the validity of the host reachability. N-Stealth... and the list goes on.
BUT if a host is denying pings from the world round and it stops trace a couple hops away
maybe a BOGON filter or ACL or........ 

Well If I can't http to it, and I can't ping it from multiple peering points, there
is a filter somewhere..  It can't even be accessed via the Worldcom UUNet network..
HMMMM..
Yeah you can telnet to it... Yeah I got to it via telnet... 
Anyway.. Normally if you can't Ping it and can't HTTP to a web server....

J
-----Original Message-----
From: alex () yuriev com [mailto:alex () yuriev com]
Sent: Tuesday, March 11, 2003 8:50 AM
To: McBurnett, Jim
Cc: chuck goolsbee; nanog () merit edu
Subject: RE: Issue with 208.192.0.0/8 - 208.196.93.0/24?


           
Is anyone from Alter.net lurking?
Just for grins I went to the DIGEX looking glass and I could 
not ping it 
from MAE-Central, PAIX , MAE-East and also from AT&T Cerf router....
below are some of the traces.. Always dies on Alter... I wonder.....
Alter? 

Brilliant. Why did not you try "telnet <target.ip> 80"?

Just because random packets spewed by traceroute are dropped 
on the floor
does not mean that the site is dead. 

Alex




Current thread: