Quote:
Originally Posted by Mark McLeod
A bridge still has a unique addressable IP and will show up as a node in a trace route.
|
Thank you.
Based on that, would it be correct to conclude that the IP address on the ethernet side of my radio (the side my router is connected to) must be 10.0.0.1, since that is the very next tracert hop after 192.168.1.1, which I know is my router ?
Would it also be correct to conclude that the radio is likely the problem, and not DNS, since I get the abnormal delay when doing only a 2-hop tracert (pc-->router-->radio), and 10.0.0.1 would not be sent to a DNS server for reverse DNS lookup?