|
Re: ping and tracert networking question
192.168.1.1 is the LAN side of my router. See the annotation in the tracert logs I included in my previous post.
I have full physical and network access to the router. I do my own router setup. That's how I was able to change the DNS server as mentioned in an earlier post.
The default gateway at the PC is 192.168.1.1 (my router). The router is set up to get an internet gateway IP dynamically. When it does so, it always gets 10.0.0.1 (the a.b.c.d in the tracert logs).
As mentioned earlier, when the problem occurs it does not go away when I bypass the router and connect directly to the radio. So the router is not the problem.
As mentioned in previous posts, I do not have any access to the radio. 10.0.0.1 gives me an AirOS login splash screen, but I do not have password access, so I cannot log in, and I can't even tell for sure if it is the AirOS radio on my roof, or an AirOS product somewhere downstream (like perhaps the local tower).
As mentioned in a previous post, I will try the "-d" tracert option next time the problem occurs. That has not happened yet.
When things are not working, there is a 60-second tracert delay even when doing tracert 10.0.0.1 (2 hops). As mentioned in the previous post, I do not know for sure if that means the problem is at the radio, or if the radio is acting as a "bridge" so that its IP does not appear in the tracert (is this what would happen with radio in bridge mode?).
The AirOS PS2 supports bridge mode. I do not know (and have no way to determine) if it is setup for that mode though.
I will try the Ubiquiti "Discovery Tool" and see what happens and report back here.
|