NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
The 2.1.2.18 nightmare
I won't bother going through how angry I am at Netgear for this firmware MESS (I already have in several posts) since they don't bother offering ANY customer support after they screw you out of your ...
I wonder why everybody seems to have problems with FW 2.1.2.18 as this is the only FW working w/o problems on my RBR20/RBS20. RBR20 is in AP mode and I need Ethernet backhaul and daisy chain option as I have armored-concrete in the ceiling between 1st (satellite) and 2nd floor (AP) and two simple switches between the AP and the satellite. Last week my whole network was down in the morning because AP and satellite had updated to 2.1.4.10. Downgraded both to 2.1.218 again, disabled auto update as described above and everything was fine.
Until today. Exactly one week after downgrading my Orbis were updated to 2.1.4.10 again automatically. And auto update is still disabled:
root@RBR20:/# nvram show | grep -E "orbi_auto_upgrade|auto_check_for_upgrade|auto_update" orbi_auto_upgrade=13064382 auto_update=0 auto_check_for_upgrade=0
Network was down again and I downgraded both to 2.1.2.18 again. Still wondering why they were updated automatically.
Did you try a reboot of the system or full factory reset and set up from scratch after it updated to v2.1.4.10?
Oceanwaves wrote:
I wonder why everybody seems to have problems with FW 2.1.2.18 as this is the only FW working w/o problems on my RBR20/RBS20. RBR20 is in AP mode and I need Ethernet backhaul and daisy chain option as I have armored-concrete in the ceiling between 1st (satellite) and 2nd floor (AP) and two simple switches between the AP and the satellite. Last week my whole network was down in the morning because AP and satellite had updated to 2.1.4.10. Downgraded both to 2.1.218 again, disabled auto update as described above and everything was fine.
Until today. Exactly one week after downgrading my Orbis were updated to 2.1.4.10 again automatically. And auto update is still disabled:
root@RBR20:/# nvram show | grep -E "orbi_auto_upgrade|auto_check_for_upgrade|auto_update" orbi_auto_upgrade=13064382 auto_update=0 auto_check_for_upgrade=0
Network was down again and I downgraded both to 2.1.2.18 again. Still wondering why they were updated automatically.
FURRYe38 wrote:
Did you try a reboot of the system or full factory reset and set up from scratch after it updated to v2.1.4.10?
I finally managed to update my RBK20 to 2.1.4.10 without breaking my network! The solution was to follow these steps and give the Orbis enough time after each step (I waited between 5 and 10 minutes).
This again shows the risks of automatic updates. As long as the update procedure can't disconnect the ethernet cable and plug it in again after waiting long enough auto update generates only problems here. I wonder whether Netgear tested the update with Ethernet backhaup at all?
Glad you go it working.
Ya I've asked about this issue. :smileyfrustrated:
Oceanwaves wrote:
FURRYe38 wrote:
Did you try a reboot of the system or full factory reset and set up from scratch after it updated to v2.1.4.10?
I finally managed to update my RBK20 to 2.1.4.10 without breaking my network! The solution was to follow these steps and give the Orbis enough time after each step (I waited between 5 and 10 minutes).
This again shows the risks of automatic updates. As long as the update procedure can't disconnect the ethernet cable and plug it in again after waiting long enough auto update generates only problems here. I wonder whether Netgear tested the update with Ethernet backhaup at all?
