Quote:
Originally Posted by Ether
That doesn't fit the given facts, unless you are claiming that tracert causes a reverse DNS to be attempted on 10.0.0.1, but what would be the point of doing that?
|
This is why seeing what -n does is interesting. I don't know for sure, one could use a tool like wireshark to sniff the flows on the wire and answer for certain (see <
http://www85.homepage.villanova.edu/...b2Exercise.pdf>) but I would not be surprised if the logic does this for any hop, regardless of the specific address. I also wouldn't be too surprised if it didn't depend on the version of tracert in question.
Quote:
Originally Posted by Ether
If 10.0.0.1 is the radio, then it is showing up in tracert.
|
In which case, it is probably doing more than just bridging (which I suspect).
The idea with pathping is to get statistics taken over a larger sample size, you might find there are drops even when things seem to be working fine -- but you need to use an address that is further out than 10.0.0.1, which is why I have been using 'chiefdelphi.com'.
If it is easy for you to do, running the util without the router in the middle could make a difference. Some packets are not forwarded across routers and the util likely uses such poackets to discover radios.
Thanks for all of the info thus far!!!