NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Enable Email Logging and Router Reboots
NOTICE:
For ANY users seeing mysterious reboots of there 7 or 8 series RBR routers rebooting at random or at specific time frames, we'd like to ask you to enable Email Logging of the RBR and config...
Ok, enabling email logs seems to help stop the RBR mysterious rebooting. Mines been online for 4+ days:
Uptime would have been more however we had a brown out last Wednesday.
This solution is looking good for me.
Basic Information
Firmware Version: V4.6.8.2_2.1.9
dumaos: v3.0.410
seal: v2.1.5.37-2
seal_services: v2.1.5.12-0
armor-bd: v2.2.100.3
spc-circle: v3.25.0.2
System Uptime: 5 days 19:29:04
When will NG come up with the firmware update that will fix the issue instead of having this ridiculous workaround? I don't want to configure my Orbi to send out emails to fix a bad firmware release.
NG doesn't publish when FW updates for forth coming. Sorry.
codejanitor wrote:
When will NG come up with the firmware update that will fix the issue instead of having this ridiculous workaround? I don't want to configure my Orbi to send out emails to fix a bad firmware release.It's ridiculous that we have to "beta test" what is a production firmware and to come up with "workarounds" just to fix Netgear's lack of quality control. Should we just hold off on this firmware update? I'm still on V4.6.8.2_2.1.9 which I had to do a factory reset/restore config to fix the web admin/app admin lock out fiasco.
- If this was any other company, they will be burning the midnight oil to find and fix the issue. With NG we will be lucky to get a "fix" in about 2 months optimistically.
If this was any other company, they will be burning the midnight oil to find and fix the issue. With NG we will be lucky to get a "fix" in about 2 months optimistically.
codejanitor If you think that Netgear is not working towards a solution for this, you are mistaken. Unfortunately, sometimes it takes a while to find the problem, then a solution to that problem, then get it tested internally and externally.
I do agree it is taking a long time but as an IT professional for over 45 years, I also know that sometimes it isn't as easy as people want to think it is - and fixing something while insuring you don't break something else can be quite tedious and difficult.
We are all looking forward to the correct solution to be provided. But I would rather wait and get the RIGHT solution, than have NG rush a fix out that causes other issues. We all know that exact thing has happened multiple times in the past and not rushing a half-baked solution is most likely the direction NG engineers have been given from higher ups.
You can update or hold on with v.2.
NG IS aware of this issue. We've made it CLEAR to them.
dtay wrote:
It's ridiculous that we have to "beta test" what is a production firmware and to come up with "workarounds" just to fix Netgear's lack of quality control. Should we just hold off on this firmware update? I'm still on V4.6.8.2_2.1.9 which I had to do a factory reset/restore config to fix the web admin/app admin lock out fiasco.