I noticed my second hop out is 0.0.0.0, with latency that indicates it's external.
(The first hop is the local gateway, as expected.)
What's up with that?
Is this the ISP's doing?
What's tracert actually pinging for that 0.0.0.0?
Personal computing discussed
Moderators: renee, Steel, notfred
meerkt wrote:Same thing with TCP.
ip route list
default via 192.168.10.1 dev wlp3s0 proto dhcp src 192.168.10.107 metric 303
192.168.10.0/24 dev wlp3s0 proto dhcp scope link src 192.168.10.107 metric 303
chuckula wrote:Another idea: Try tracepath instead of traceroute.
I have a relatively wacky ISP myself here and tracepath seems to work fine.
The tracepath utility is part of the iputils package that's widely installed in many Linux distros, although once again I don't know if it is available for Windows [if that's your OS].
meerkt wrote:The thing is, I don't recall ever seeing something like this, on this ISP or any other.
I did search the web some, but no obvious relevant answer.
No Bonjour here. And wouldn't that entail 0 latency?
On Windows there's "route print" for some routing info. It seems normal, comparing to random stuff on the web.
No tracepath on Windows. What specific feature of it you think may be of help? But if even if that sidesteps the strangeness, I'm curious to know what/why/how the common tools show.