NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi MR 2.1 Update 3/23/18
Our teams are still working through the issues, but I wanted to provide a quick update on OrbiOS 2.1. We usually wait to release our software until it's available across all Orbi product lines, but ...
May very well be why they asked me to participate ....
I have Windows, Parrot, Roku's, Apple, Android, Raspberry Pi and a host of other devices running on my network ...
How is your system configured?
What channels are you using?
Did you upgrade FW and is Beamforming, Mimo, Daisy Chain, Fast Roaming and IPv6 enabled or disable?
Whats the distance between the router and satellite?
Is 20/40Mhz Coexistence enabled?
steve8411 wrote:May very well be why they asked me to participate ....
I have Windows, Parrot, Roku's, Apple, Android, Raspberry Pi and a host of other devices running on my network ...
When doing a FW upgrade, do you lose all the labeling of devices, setup parameters? It was a ton of work just setting this thing up. It is by no means a PnP product, and I'm technically inclined...
Dear fellows in misery,
All the follwing applies only WHEN IN AP MODE!
Some relief comes from wired ethernet backhaul. I guess it is because of saved 5G bandwidth. Who knows.
However, problem was to run an extra cat 6 cable through the flat - next to the already existing LAN wired infrastructure.
Why is this an issue?
Well because the Netgear documentation - same crappy&confusing as the firmware - advises to use the yellow WAN port. Wrong.
As for ethernet wired backhaul in AP mode, use 1st LAN port - right next to the yellow one.
(no idea if this has influence but Daisychain Off, Beamforming On, MU-MIMO On, Fast Roaming On and :smileyfrustrated:Yes Yes Yes I did paper-clip factory reset the cheesy orbi router + satellite after firmware migration to 2.1.3.4)
=> this doesn't hinder Orbi junk from internet drops or lost connections but it reduces them
Cheers, Volker
PS
There is an entire thread for this:
https://community.netgear.com/t5/Orbi/Ethernet-Backhaul-Best-Practices/m-p/1486919#M21278
PPS
I also liked this reddit blog entry to find out the satellite backhaul type via telnet:
https://www.reddit.com/r/orbi/comments/7jfdhk/ethernet_backhaul_howto/
If you upgraded to v2.1.3.4, yes all settings will be erased. This is for only this version. These are beta and there are differences in FW from last version to beta. We see that other users reported continued problems after the update however didn't reset the router and set up from scratch. After doing a reset and set up again, the problems not longer appeard. Im told that going forward, NG is aware of this and next future updates users should not have to reset and set up from scratch after doing a FW update.
mmiguy wrote:When doing a FW upgrade, do you lose all the labeling of devices, setup parameters? It was a ton of work just setting this thing up. It is by no means a PnP product, and I'm technically inclined...
So did chaning from WAN to LAN port resolve your problems?
Planetom wrote:Dear fellows in misery,
All the follwing applies only WHEN IN AP MODE!
Some relief comes from wired ethernet backhaul. I guess it is because of saved 5G bandwidth. Who knows.
However, problem was to run an extra cat 6 cable through the flat - next to the already existing LAN wired infrastructure.
Why is this an issue?
Well because the Netgear documentation - same crappy&confusing as the firmware - advises to use the yellow WAN port. Wrong.
As for ethernet wired backhaul in AP mode, use 1st LAN port - right next to the yellow one.
(no idea if this has influence but Daisychain Off, Beamforming On, MU-MIMO On, Fast Roaming On and :smileyfrustrated:Yes Yes Yes I did paper-clip factory reset the cheesy orbi router + satellite after firmware migration to 2.1.3.4)
=> this doesn't hinder Orbi junk from internet drops or lost connections but it reduces them
Cheers, Volker
PS
There is an entire thread for this:
https://community.netgear.com/t5/Orbi/Ethernet-Backhaul-Best-Practices/m-p/1486919#M21278
PPS
I also liked this reddit blog entry to find out the satellite backhaul type via telnet:
https://www.reddit.com/r/orbi/comments/7jfdhk/ethernet_backhaul_howto/
FURRYe38 wrote:So did chaning from WAN to LAN port resolve your problems?
Planetom wrote:Dear fellows in misery,
All the follwing applies only WHEN IN AP MODE!
Some relief comes from wired ethernet backhaul. I guess it is because of saved 5G bandwidth. Who knows.
However, problem was to run an extra cat 6 cable through the flat - next to the already existing LAN wired infrastructure.
Why is this an issue?
Well because the Netgear documentation - same crappy&confusing as the firmware - advises to use the yellow WAN port. Wrong.
As for ethernet wired backhaul in AP mode, use 1st LAN port - right next to the yellow one.
(no idea if this has influence but Daisychain Off, Beamforming On, MU-MIMO On, Fast Roaming On and :smileyfrustrated:Yes Yes Yes I did paper-clip factory reset the cheesy orbi router + satellite after firmware migration to 2.1.3.4)
=> this doesn't hinder Orbi junk from internet drops or lost connections but it reduces them
Cheers, Volker
PS
There is an entire thread for this:
https://community.netgear.com/t5/Orbi/Ethernet-Backhaul-Best-Practices/m-p/1486919#M21278
PPS
I also liked this reddit blog entry to find out the satellite backhaul type via telnet:
https://www.reddit.com/r/orbi/comments/7jfdhk/ethernet_backhaul_howto/
It eased the pain didn't solve