Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Tue Jun 14, 2022 16:54 Post subject:
This is like I said a weird issue.
Just on the latest report thread we have someone with the r9000 without these issues and then one with these issues.
matjazk as already posted has the issues and tried reset couldn't fix it and johnnyNobody999 with same router has none of these issues.
Mlandi had these issues and fixed it... other users also dont have this issue like johnnyNobody999, so tbh you cant all be right/wrong its the same router, the only variables are user specific OS version/Browser combos maybe something else in addition.
Yet still no one coming forward with the information requested earlier in this thread. Trying to find common denominators between the different users with the router, in order to see if this is somehow related to specific external causes, seems to be unwanted by anyone with the issues.
honestly dont know, i disabled it prior to the issues reported, only know that it does it cause i accidently went to configure the wrong radio a couple of times.
A quick search for clues. The AD 60GHz radio doesn't seem to have ever been given functional support as best I can surmise. It also is apparent that the design vs. how the device is put together is problematic. As a result, "hardware failure" can result in the wireless tab going missing.
Joined: 21 Aug 2019 Posts: 120 Location: Here, There And Everywhere
Posted: Tue Jun 14, 2022 21:55 Post subject:
Well, thank you all for useful hints.
I went back to r44810, configured my usual staff, and, as per hints, disabled wlan2 and airtime fairness. Upgraded to r49197 and voila, wireless basic settings loaded in full.
Then I enabled wlan2 [60GHz 802.11ad] and the wireless tab crashed immediately. The situation was quickly remedied by
Code:
nvram set wlan2_net_mode=disabled
nvram commit
reboot
So it seems that enabling the 60 GHz radio is indeed the culprit.
Joined: 15 Aug 2016 Posts: 223 Location: Melbourne, Australia
Posted: Tue Jun 14, 2022 23:13 Post subject:
That was also what i found earlier while setting up VLANs on R9000. So i disabed wlan2 (60GHz).
Here are a few more observations/tips:
For a start, Netgear R9000 is an unusual wireless router with two internal switches, requiring an unusual approach to tackle it.
- R9000 takes longer to boot up.
- Keep your eyes on the four indicator lights (starting from Power) between changes, especially when R9000 defaults back to 192.168.1.1 and needed to be restored to a previous cfg backup. I had to wait patiently for another good 10-15 seconds after the normal lights are back, before wired connection can be established. The wait may not be that long in your case since I have VLANs via bridges and OpenVPN Client running on mine.
- Don't use power off/on button of R9000 for reboot. It does not always restore it to a full-operating mode. Instead, reboot via software:
*** Administration/Management/Reboot Router tabs.
(If unable to access its web GUI from wire after reboot, use wireless. It should connect you to its web GUI. Sometimes you must try connecting it TWICE, in succession, for the wireless connection to stay on).
Its pages should be back to normal. This has always been the case with my R9000.
P.S. My R9000 has been working fine since i allow for its peculiarities, when necessary.
Good luck. _________________ Life is a journey; travel alone makes it less enjoyable and lonely.
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Wed Jun 15, 2022 9:59 Post subject:
Question is will that also take care of missing UI elements, I guess we will soon find out.
If it doesn't then my theory has to be proven/disproved. Something on the back of my brain screams Windows 11, yep, Im traumatized by MS and this latest flop.
Joined: 06 Jun 2006 Posts: 7445 Location: Dresden, Germany
Posted: Wed Jun 15, 2022 10:02 Post subject:
matjazk wrote:
Well, thank you all for useful hints.
I went back to r44810, configured my usual staff, and, as per hints, disabled wlan2 and airtime fairness. Upgraded to r49197 and voila, wireless basic settings loaded in full.
Then I enabled wlan2 [60GHz 802.11ad] and the wireless tab crashed immediately. The situation was quickly remedied by
Code:
nvram set wlan2_net_mode=disabled
nvram commit
reboot
So it seems that enabling the 60 GHz radio is indeed the culprit.
