NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
FURRYe38
Aug 11, 2022Guru - Experienced User
New - RBR350 / RBS350 Firmware Version 4.4.1.29 Released
New Features and Enhancements: 08/09/2022
IPv6 DS-Lite, MAP-E support
Analytics opt-in/opt-out for EU region
VLAN ID and DHCP options 60/61 support
Admin password strength enforcement
Adm...
Supersjel
Oct 01, 2022Guide
Hi,
Did the update (first satelites, second router including factory reset after updates) but have some problems. Configuration is RBR350 (AP mode) and 2 RBS350 satelites behind a Fritzbox 7590 modem. Everything works for the "normal" network both with wireless and wired backhaul. The guest network only works with the wireless backhaul. When I connect the cables to the satelites the guest network is up and config pages show normal status but connected devices loses internet connection.
With the previous firmware version the guest network also worked with the wired backhaul. Is this a bug? Or did I miss something and are other changes required to get this working with this firmware version?
FURRYe38
Oct 01, 2022Guru - Experienced User
Are the RBS connected to the RBR? In back of the RBR or is there a network switch in between?
What CAT# lan cables are you using? CAT6 is recommended.
Did you sync the RBS first to the RBS wirelessly then after the BLUE LED appears, then connect the RBS to the RBR via ethernet?
Give several minutes for the RBS to sync fully and the front LED to turn OFF.
Supersjel wrote:
Hi,
Did the update (first satelites, second router including factory reset after updates) but have some problems. Configuration is RBR350 (AP mode) and 2 RBS350 satelites behind a Fritzbox 7590 modem. Everything works for the "normal" network both with wireless and wired backhaul. The guest network only works with the wireless backhaul. When I connect the cables to the satelites the guest network is up and config pages show normal status but connected devices loses internet connection.
With the previous firmware version the guest network also worked with the wired backhaul. Is this a bug? Or did I miss something and are other changes required to get this working with this firmware version?
- SupersjelOct 02, 2022Guide
Thanx for the reply! I'll try to answer the questions
FURRYe38 wrote:What CAT# lan cables are you using? CAT6 is recommended.
It's (unshielded) CAT6 cables. But I can't imagine the cable is the problem. Because if it was ... (my logic) ... I would think both the normal and guest network wifi would fail. But the outcome for the cabled setup is only the guest network is not working.
FURRYe38 wrote:Did you sync the RBS first to the RBS wirelessly then after the BLUE LED appears, then connect the RBS to the RBR via ethernet?
Yes, found on this community in a post this is important so I did. Even let it run for 10 minutes with some tests on the clients to see if it was stable.
FURRYe38 wrote:Are the RBS connected to the RBR? In back of the RBR or is there a network switch in between?
Last but not least the most interesting question, read a lot about this after the purchase six months ago. The manual of the Orbi's misses good documentation on wired setups. I have a netgear gigabit switch and read some contradicting information. So with the old firmware I just tested a few setups.
- modem -> orbi router -> orbi satelites (i.e. connecting satelites through router): worked
- modem -> switch -> orbi router -> orbi satelites (i.e. connecting satelites through router): worked
- modem -> orbi router & orbi satelites (i.e. connecting both router & satelites on modem): worked
- modem -> switch -> orbi router & orbi satelites (i.e. connecting both router & satelites on switch): worked
- modem -> orbi router -> switch -> satelites : instable (and undesired because the Orbi doesn't support IP-TV over network).
With some variations:
- Connecting the orbi router (in AP mode) through WAN or LAN did make no difference (except for blinking led if LAN is used)
- Connecting the satelites made difference, I read somewhere the LAN port on the right/most distance to power connection must be used.
I think 1/2 are the official ones (the "downstream option"). But since 4 lead to the optimal placement (best coverage) so I chose that. And used that until the firmware upgrade.
So this question reminds me of something. Don't remember which LAN port on the satelite I used yesterday. Double check that. And maybe this working setups changed with the new version and I should revisit option 1/2? Or is there another setup that I missed?
- SupersjelOct 02, 2022Guide
Supersjel wrote:So this question reminds me of something. Don't remember which LAN port on the satelite I used yesterday. Double check that. And maybe this working setups changed with the new version and I should revisit option 1/2? Or is there another setup that I missed?
Meanwhile tried 2 things that don't require lots of work:
- Changing the LAN port of one of the satelites (left the other wireless backhaul). No difference. After the lights blinked, blue and off again and the webpage showed wired backhaul ... the normal wifi network works but the guest network shows "no internet" on clients
- Changing the connection of one of the satelites (left the other wireless backhaul) to #2 (so modem -> switch -> Orbi Router -> CAT 6 -> Satelite. Normal wifi still works. Guest network works "a little" meaning severe delays and connection loses. So highly unstable and unusable.
And one new question, maybe this configuration (wired backhaul, AP mode and guest network) just isn't supported anymore in this firmware version. Is flashing router and satelites to the previous version 4.4.0.10 an option?
- FURRYe38Oct 02, 2022Guru - Experienced User
Supersjel wrote:
Thanx for the reply! I'll try to answer the questions
FURRYe38 wrote:What CAT# lan cables are you using? CAT6 is recommended.
It's (unshielded) CAT6 cables. But I can't imagine the cable is the problem. Because if it was ... (my logic) ... I would think both the normal and guest network wifi would fail. But the outcome for the cabled setup is only the guest network is not working.
FURRYe38 wrote:
Did you sync the RBS first to the RBS wirelessly then after the BLUE LED appears, then connect the RBS to the RBR via ethernet?
Yes, found on this community in a post this is important so I did. Even let it run for 10 minutes with some tests on the clients to see if it was stable.
FURRYe38 wrote:
Are the RBS connected to the RBR? In back of the RBR or is there a network switch in between?
Last but not least the most interesting question, read a lot about this after the purchase six months ago. The manual of the Orbi's misses good documentation on wired setups. I have a netgear gigabit switch and read some contradicting information. So with the old firmware I just tested a few setups.
- modem -> orbi router -> orbi satelites (i.e. connecting satelites through router): worked
- modem -> switch -> orbi router -> orbi satelites (i.e. connecting satelites through router): worked
- modem -> orbi router & orbi satelites (i.e. connecting both router & satelites on modem): worked < I Would use this configuration if this worked for you.
- modem -> switch -> orbi router & orbi satelites (i.e. connecting both router & satelites on switch): worked
- modem -> orbi router -> switch -> satelites : instable (and undesired because the Orbi doesn't support IP-TV over network).
With some variations:
- Connecting the orbi router (in AP mode) through WAN or LAN did make no difference (except for blinking led if LAN is used)
- Connecting the satelites made difference, I read somewhere the LAN port on the right/most distance to power connection must be used.
What is the model# of this switch?
Seems like the GN is working in some variations which means the FW is probably ok but how the configuration and switch is being implemented maybe causing the bad behavior.
This would be the recommended connection of the RBS using ethernet to the RBR if a switch is in the mix and in between the RBR and RBS:
What mode is the modem working in? Router or Modem mode only?
- SupersjelOct 03, 2022Guide
Thanx again for your time!
FURRYe38 wrote:What is the model# of this switch?
It's a Netgear GS116Ev2
FURRYe38 wrote:Seems like the GN is working in some variations which means the FW is probably ok but how the configuration and switch is being implemented maybe causing the bad behavior.
I'm a bit worried. Changed nothing in hardware/wiring and the new firmware broke the guest network. Not meaning of course there's no way to fix it again.
FURRYe38 wrote:
This would be the recommended connection of the RBS using ethernet to the RBR if a switch is in the mix and in between the RBR and RBS:Thanx for the link. It was already in my favorites collection. To be on the "official" page I just tried the first setup.
- I cripled my network by disconnecting the router. So now it's just the modem.
- I connected the Orbi router to it.
- Power cycle to be sure.
- Waited for it to be up again.
- Activated one satelite, first wireless backbone. Waited for the lights to go down.
- Ran a test, perfect connection on both normal and guest network.
- Connected the satelite with a cable to de Orbi router (same as shown on your link)
- Waited again for led to go off and webpage to show a wired backhaul
- Ran the test again, but unfortunately same result. Normal network running, guest network very unstable. It keeps resetting connections to clients.
- To be sure ... disconnected cable. Worked perfect again. Connected with another cable, guest network bad again.
(previous setup with both router and satelite connected to modem is even worse. Than the guest network is not working at all.
FURRYe38 wrote:What mode is the modem working in? Router or Modem mode only?
The Orbi router is in AP mode meaning the modem itself is in router mode. Needs to be, else the IP-TV and telephony from the provider is not working. Too technical for me but I read somewhere this is because the Orbi doesn't support VLANs needed for this.
Hope you have some ideas left, else a downgrade seems the only solution to me. The second satelite is a bit to far away from the router. So with a wireless backhaul is will periodically lose connection.