[OLUG] Don't rely on Ping.

Drazak drazak at moongate.net
Tue Jan 11 04:34:18 UTC 2000


I keep seeing people recommending Pinging different locations to
troubleshoot problems.  Again, you cannot rely on ping working much
anymore on todays Internet, especially where NAT and IPmasq is going on. 
Both of the boxes where I have my shell accounts block pings using
ipchains, and my DSL router as configured from Navix blocks it as well. 
Also, the NAT software on my Cisco Comp router at work also blocks pings. 
In fact, to diagnose problems I have to run my traceroutes from the router
itself, not my normal workstation behind the router. 

For example, here is a log from my linux box at home.  Its hooked right
into the 675 DSL router.  Im running no firewalling on my box at all.  As
you can see, i can lookup addresses and have perfect connectivity, but
cannot ping.  


bash$ nslookup calvin.nebrwesleyan.edu 
Server:  iac14.navix.net 
Address: 207.91.5.20
 
Non-authoritative answer:  
Name:  calvin.nebrwesleyan.edu 
Address: 192.94.109.2
 
bash$ ping calvin.nebrwesleyan.edu 
PING calvin.nebrwesleyan.edu (192.94.109.2) from 192.168.200.2 : 56(84)
bytes of data. 
 
--- calvin.nebrwesleyan.edu ping statistics --- 3 packets transmitted, 0
packets received, 100% packet loss 

bash$ telnet calvin.nebrwesleyan.edu
Trying 192.94.109.2...  
Connected to calvin.nebrwesleyan.edu.  Escapecharacter is '^]'. 
 
 
SunOS 5.7
 
login:  

telnet> close Connection closed.  






-------------------------------------------------------------------------
Sent by OLUG Mailing list Manager, run by ezmlm.  http://olug.bstc.net/ 
To unsubscribe: `echo unsubsribe | mail olug-unsubscribe at bstc.net` 



More information about the OLUG mailing list