North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Pingable IPs on backbones?
I just had one of those "duh" experiences today, and it made me think a bit... At my job at <vijay> a promising local ISP </vijay>, I was turning up a customer, who decided to test his connectivity by trying to ping and trace to www.sprint.net and www.uu.net. As it turns out, both servers are behind firewalls, that block ICMP and UDP, so you can't ping or trace to either server. But then my customer asked me, "OK, can you give me a hostname in UU's netspace that I CAN ping?" It took some thought and experimentation to find one (mail.uu.net and ns1.sprint.net, in case anyone wants to know). What this brought to mind was this question: would it be worth my time to compile a list of pingable and traceable IPs that live on the major backbones for connectivity testing and troubleshooting? I do wind up seeing a lot of cloobies trying to ping a site, and assuming it's down because IMCP-blocked. Thoughts? -C --------------------------- Christopher A. Woodfield email@example.com PGP Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xB887618B