Ping does work, though surprisingly long and erratic latency.
about ping… good…
Latency? WiFi standard…
At wifi settings… you can increase the power TX/RX of both devices. MAYBE help.
Signal are good, looking the picture.
So…
192.168.130.1 know the path to 192.168.130.129 (behind 192.168.130.2)
AND?
Any device ( computer ) behind the lan of 192.168.130.129?
Can you ping this device from 192.168.130.1 (system/ping)?
Can you ping this device from lan of 192.168.130.129?
Well, at the moment the BaseStation3 and Rover BR1 radios are about 10 feet/3m apart, so transmitting power better not be an issue!
So yes, 130.1 can ping 130.129. But 130.1 cannot ping 130.147, which is the computer that is hard-wired to Rover. 130.147 does respond to pings from 130.129.
Hi… the default gateway of 130.147 is 130.129 and his netmask /25 (255.255.255.128)?
It seems that way! Some results from the command “ip route”. Note that the computer’s IP has changed to .141:
default via 192.168.130.129 dev br0 proto dhcp src 192.168.130.141 metric 100
192.168.130.128/25 dev br0 proto kernel scope link src 192.168.130.141
192.168.130.129 dev br0 proto dhcp scope link src 192.168.130.141 metric 100
Looking pictures… don’t see errors…
You reboot both devices? after chance both?
Yup, I’ve rebooted many times throughout this process. I agree, there don’t seem to be any errors. It’s a real mystery at this point, as to why data isn’t getting through!
Do you have setup any outgoing rules?
No, I don’t have any other rules set up aside from what was discussed in this topic.
There is something wrong… But I don’t know what.
I did here… and works… and also… use with Peplink and Teltonika… same way… works with both vendors.
Admin - Device 192.168.130.1/25
All devices under it, has the default gw it. Correct?
Doing traceroute from a device under 192.168.130.1, going to 192.168.130.141?
Please… can you share the result?
H:>tracert 192.168.130.141
Tracing route to 192.168.130.141 over a maximum of 30 hops
1 1 ms * 2 ms max-br1-2bd0 [192.168.130.1]
2 104 ms 6 ms 5 ms 192.168.130.2
3 * * * Request timed out.
4 * * * Request timed out.
I thought this was interesting:
H:>tracert 192.168.130.129
Tracing route to 192.168.130.129 over a maximum of 30 hops
1 2 ms * 2 ms max-br1-2bd0 [192.168.130.1]
2 86 ms 6 ms 6 ms 192.168.130.129
Trace complete.
I think we might have a success here! I completely cleaned out all the old DNS addresses on the computers involved, and made sure they weren’t grabbing addresses from anywhere else. Once I did that, everything started talking as expected. I’ve got a few more tests to do but this is looking very good!
2 Likes