Quote:
Originally Posted by spuggy
An ICMP issue does not indicate a TCP/IP problem. IP may have an issue that also affects ICMP - but failure of any external network hop to design to talk ICMP to you is not a problem.
Many network operators won't pass ICMP outside their network. Although many NSPs will.
|
I know that. Traceroute is a good tool to start your troubleshooting with and it's available to the OP. While it has limitations it's not a useless tool. Many operators configure their routers to not respond to icmp traffic but they will forward them to the next hop. That's how you get the broken traceroute returns that ultimately get to the destination. It just depends on the network.
The other tools available that can perform TCP scans (like nmap, Hping) require specialized knowledge and so would not be helpful to him. Not to mention that most system owners don't like people scanning their system.
Quote:
Originally Posted by spuggy
So, you work(ed) for Zayo, are familiar with the internal device naming nomenclature/topology of their network and can thus definitively identify the routing issue there from some number of unidentified nodes that don't respond to public ICMP?
Oh, that's not right? OK.
|
Why the attitude?
And how did you come up with all of that? I never identified an issue. I simply said it was bouncing around Zayo's network. Perhaps I should've said "it certainly looks like it's bouncing around Zayo's network" - probably would have read better. But that was more of a tongue-in-cheek commentary on the number of hops. I work for a 40k user organization in silicon valley - I'm not used to seeing that many hops on our network.
And just for kicks I did an experiment. I think there were 11 hops on the OP trace route - 6 just inside Zayos network. I was able to do a traceroute to a DNS server in Wandsworth United Kingdom in 13 hops (212.118.241.1) with no breaks between routes.
Anyway - the OP trace route shows it leaving OP's home network. Enters and exit COX network at 68.105.30.150 and 64.125.25.122. Enters Zayos at 64.125.25.122 after which all subsequent hits are Zayos:
64.125.29.52
64.125.28.98
64.125.29.48
64.125.30.247
64.125.25.129
So doesn't seem to be an issue with COX. Seems like an issue between Zayos and whatever comes next.
One thing is certain - none of us know what the issue is and none of us are in a position to fix it.
One other certainty is there are some big ego's here judging by the attitudes in some of these posts. Wow.
