Quote:
Originally Posted by nuttle
could just be marginal alignment
|
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?
Quote:
|
the antenna is highly directional
|
It has to be. It's pulling in an 802.11 signal from over a mile away.
Quote:
|
....strong indication that you are seeing the rooftop radio at 10.0.0.1... any DNS operation has to contact a server on the Internet
|
It sounds like you are saying tracert 10.0.0.1 causes a reverse DNS operation to be attempted on 10.0.0.1
Are you quite sure of that? It seems pointless to do that.
Quote:
|
If they let you access the admin UI for the radio, you could probably tell a whole lot more.
|
For sure.
Quote:
|
If there's an option to use your own radio
|
No. That's not their business model.
Quote:
|
I assume you tried ubnt/ubnt to log into the radio?
|
That is the default for this model radio, and it was changed during installation. As mentioned previously, I do not have the password.
Quote:
|
Did the utility tell you anything?
|
No. See attached screenshot.
Quote:
|
the fact that you can bring up a login screen is another strong indication that you are seeing the rooftop radio at 10.0.0.1 ... A bridge will typically have a layer 3 IP address, but it doesn't follow that it is going to show up in tracert.
|
If 10.0.0.1 is the radio, then it
is showing up in tracert.
Quote:
|
If you are using Windows, try the pathping command -- it is more informative than tracert
|
More informative in what way? See below:
Code:
C:\>pathping 10.0.0.1
Tracing route to 10.0.0.1 over a maximum of 30 hops
0 Ether [192.168.1.33] <--my PC
1 192.168.1.1 <--my router (LAN side)
2 10.0.0.1 <--my radio?
Computing statistics for 50 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Ether [192.168.1.33]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 1ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1
Trace complete.
C:\>