NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New - RBR850/RBS850 Firmware Version 4.6.9.11 Released
RBR850/RBS850 Firmware Version 4.6.9.11 Released
New Features:
Adds an auto-firmware upgrade enable/disable option <Long awaited feature is FINALLY HERE!
https://kb.netgear.com/...
Seanster wrote:I have not reserved an IP
When the RBS is wired, it obtains an IP address (which is the exact same IP address that it had before I reset it).....when it is not wired, that seems to fail. So your suggestion is to reserve IP's for everything ?
Just reserve an IP address to the satellite that you have problem with. Check the MAC address written on the back of the satellite and reserve an IP for that MAC in the ISP router.
This will solve the problem if the satellite can find the DHCP server, but if it can't find the DHCP server then this will not help.
I think that this is an issue that was introduced in 4.6.9.11 that teh satellite will not find the DHCP server when it's connected wirelessly with the router. Seems that the issue is in the router, seems to somehow forget that's in AP mode. Please test to set Orbi in Router mode and click Apply then change it back to AP mode and click Apply. This might remind the router to point the satellite to the correct DHCP server.
Ok so latest status.....tldr
Hit the AP button on the router website just to see if this would do anything like 'remind the router it was in AP mode' - it rebooted the router but none of the problems disappeared. Still unable to add or re-sync the factory reset satellite, and both other satellites showing as disconnected (but seemingly still functioning)
So I rolled back the firmware to 4.6.8.5 and......still the same. All satellites are disconnected, cannot add/sync the factory reset satellite. So let's go back to basics. Power down all satellites, power down the unmanaged switch which serves to provide wired backhaul, pull all ethernet cables from the satellites. Reboot router, and then power on 1 satellite to see if it comes up in wireless backhaul. Nope. This also does not work, magenta ring LED. I am now completely out of ideas.
Unless anyone has anything else I should try, I think I need to start from scratch (which I've never done and am terrified of.....)
Seanster wrote:...... Nope. This also does not work, magenta ring LED. I am now completely out of ideas.
......
In the web GUI (orbilogin.com) under Attached Devices, do you see the satellites marked as offline? If yes, then there should be a "Disconnect" button beside, click it to remove old pairing and try again please.
I did this with the first Satellite yesterday - removed it from the RBR GUI, rebooted it and it did not come back up on the screen. Only way to get it back is to wire it directly to the RBR
Seanster wrote:I did this with the first Satellite yesterday - removed it from the RBR GUI, rebooted it and it did not come back up on the screen. Only way to get it back is to wire it directly to the RBR
Ok, wire it, then switch it off, then you will see the "Disconnect" button on the Attached Devices" page. Please click it to un-pair the satellite and try now to pair it wirelessly.
Ok I am going to work with the Satellite that has been factory reset, as this one needs to get working. Powered up the RBS, solid white light, attached it via Ethernet to the RBR. Within a minute the ring LED goes solid blue. Here's what I see on the RBR GUI:
And here's what it looks like when I go directly to the RBS:
As you can see, it is still sitting on the ORBI default SSID
Disconnected the Ethernet cable, turned the RBS off. Deleted the entry on the RBR GUI for the RBS. Powered the RBS back up again, flashed white for a while then solid white ring LED. pressed sync button on back of RBS and back of RBR. Both flash white for about a minute. RBS then stops flashing, and shortly thereafter the RBR stops flashing, both go dark for about 30-40 seconds then RBS goes solid magenta....
All are on 4.6.8.5, rolled it all back this morning
BUT...making progress
Still working through this, a very interesting explanation coming up of what I think happened...
So, we have a much nicer picture now!
So exactly what was the issue?
Well there were 2. As one of the helpers here pointed out, it appeared my factory reset but seemingly bricked RBS was, in fact, not getting an IP address. But the fun part is why it was not getting an IP address.
My wired backhaul setup has an unmanaged switch behind the RBR, which then connects to each RBS. However, when I set this up a couple of years ago there were major problems and I could not get it to work. However on one of the forums I found a tip, to wire the connection from RBR to the switch via the WAN port, and plug the internet connection into any other of the Ethernet ports on the RBR.
Well that worked fine until now. Once I ripped everything down to the minimum (just what I thought was a direct connection from ISP modem to RBR) showed me solid magenta on the RBR....no IP. This was the ethernet cable going to the unmanaged switch. Plugging the 'correct' cable into the RBR Wan port kinda solved all current issues.
So now I do not know if .11 introduced this, or if this was a previous firmware and I was just oblivious to it (as things 'appeared' to be working) - but somewhere along the line the functionality of the RBR Wan port has been changed to what would be 'expected behaviour'
Thank you ALL for your help here!
Please edit out any MAC addresses from your pictures before posting in a public forum for security reasons.
To ensure that RBS are updated properly, update ALL RBS first to v.11 then the RBR lastly.
Seanster wrote:
All are on 4.6.8.5, rolled it all back this morning
BUT...making progress
Still working through this, a very interesting explanation coming up of what I think happened...
