NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
zombywoof
Oct 04, 2024Aspirant
RBR750 ap mode wired backhaul, wan port=internet/no synced sats, lan port=no internet/synced sats
I'm stuck. I have a RBR750 and 2 RBS750 satellites. All are upgraded to firmware V7.2.6.31(_5.0.24). I did a reset on all devices and started out new. First I've set the RBR to AP mode and choose d...
- Oct 04, 2024
Fixed it.đ
I went back to firmware V4.6.14.3_2.3.12, didnt even reset to factory, kept all settings and all problems disappeared.
Now i can connect to the RBR LAN port.
I'm able to ping the RBR perfectly
The RBR sees and syncs the satellites over wired backhaul over multiple switches.
The wireless clients get 500-600 Mbps internet everywhere in the house
Conclusion: the firmwares above V4.6.14.3_2.3.12 destroy AP mode.
FURRYe38
Oct 04, 2024Guru - Experienced User
So go my RBK752 system up and running.
First off was RBR in router mode to make sure RBS wireless and ethernet connected to the RBR.
HP 1400 series non managed switch used in between.
Then configured AP mode and use a RAX80 for host router.
Left RBS ethernet connected to switch and switch connected to RBR after applying AP mode configuration:
Gave several minutes for everything to settle in. 192.168.1.75 IP static IP address used on RBR for AP mode:
RBR AP mode connected devices page:
RBS web page:
RBS connected devices page:
Ping results with ethernet connected PC behind the RBR:
Ping results with same ethernet connected PC behind the HP LAN switch connected behind the RBR:
zombywoof
Oct 05, 2024Aspirant
In your picture:
Also remarkable, with 7.2 it does not show it's IP. With 4.2 it does show it's IP.
- FURRYe38Oct 05, 2024Guru - Experienced User
Ya thats a bug we found back on v.21. Reported it. Still on going. Doesn't effect much. Just a UI display issue.
- zombywoofOct 05, 2024Aspirant
Yeah i know, it does have the IP. Its just remarkable.
V31 also btw
BTW, your ping should be ping -t
In my issue as described above the problem was: it gave 7-10 good replies but then came 7-10 timeouts
- FURRYe38Oct 06, 2024Guru - Experienced User
Ran this for this period of time then also let it run while I was typing up this post to respond, about 2 minutes, saw no issues while it was pinging:
Ping statistics for 192.168.1.75:
Packets: Sent = 130, Received = 130, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 14ms, Average = 0ms