NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R8000P Latest "breakware"...AGAIN!
Well, here we go again! Folks, do not update this doorstop to 1.4.2.84 without copying down on paper ALL your custom settings and stuff because you will likely need them after you update and hard res...
I eventually had to rollback as well. Strange how I didn't have issues for nearly 6 weeks and suddenly, DNS resolution began faultering.
I tried re-flashing, restoring a back up .cfg created from the original branch, but the behavior continued. I then reset and tested upgrade to 1.4.2.84 from a unmodified flash of 1.4.1.68, same behavior. At this point, I recommend going back or holding at 1.4.1.68
And yes Mr. Guru.....I know what I'm doing and what I am saying. I am not here for some months long discussion of try this, try that, blah, blah, blah. I am here to forewarn poor disfortunates that bought one of these too. Anyone that has ever flashed ANYTHING successfully as many times as I have, knows the procedure and foresteps to take to insure a sucessful flash provided everything is electrically sound and the firmware coder wasn't smoking dope while coding.
Good Luck to you also.
I'm not the type to pile on but Bob is right. I had not issues, but upgraded to the newest firmware for my R8000P as it stated it fixed security issues. and now I get this message from my browser all the time. this is from this forum went I wanted to reply to this post. I have struggled to check if the issue was with browsers, my security, etc. but all comes back to this firmware update.
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
What FW version had you been using prior to the update?
Has a factory reset and setup from scratch been performed since last FW update?
njmoleman wrote:
I'm not the type to pile on but Bob is right. I had not issues, but upgraded to the newest firmware for my R8000P as it stated it fixed security issues. and now I get this message from my browser all the time. this is from this forum went I wanted to reply to this post. I have struggled to check if the issue was with browsers, my security, etc. but all comes back to this firmware update.
- That screen you are getting in your browser is BAD FIRMWARE! Revert back to previous fw and it will work as designed. As for the “questions” READ READ READ! Modem is set to PASS-THROUGH. If you connect straight to the modem bypassing the router, all is fine with the modem. Problem is dope smoking coders and ZERO NADA ZILCH BETA TESTING on new releases and management PUSHING for a release! Tired of being fleeced by these “reputable” companies with less that average products and, like the testing, ZERO NADA ZILCH SUPPORT!!
As stated, nothing has changed except the firmware. And just to add on, the modem is a Netgear CM2050 and the provider is Xfinity. There has been no firmware update on the modem. the issue is for every computer on the LAN side including phones and tablets. BTW I'm a network admin. I have a test enviroment to that I run all updates through before rolling them out to production devices. I would hope that Netgear does the same, and this is somehow yet another fluke and not a "good enough" update.
I eventually had to rollback as well. Strange how I didn't have issues for nearly 6 weeks and suddenly, DNS resolution began faultering.
I tried re-flashing, restoring a back up .cfg created from the original branch, but the behavior continued. I then reset and tested upgrade to 1.4.2.84 from a unmodified flash of 1.4.1.68, same behavior. At this point, I recommend going back or holding at 1.4.1.68
Greetings,
I've been running v1.4.2.84_1.3.42 since November 1st. Its stable. No performance issues here.
I do routinely make a back up of my config before upgrading (manually) and then another after the update, but haven't had any issues. I also have customized settings everywhere.
There are still certain features like renaming attached devices, etc which I have abandoned because they have been broken for so long.
However, over all performance and stability (wired and wireless) is fine.
For the DNS Error above I would:
Flush my DNS cache
Ensure my DNS settings matched those of my ISP, Cisco Umbrella, Cloudflare, etc. I don't normally use public DNS but you can if you wish.
Verify my DNS is resolving correctly.
- And furthermore….if they have ANY issues with ANY ARRIS modems then there are A LOT of people with this brick having the same issues. It’s BAD FIRMWARE…period.
Bob,
You seem to be very upset. Sorry your experience hasn't been a good one. My Arris modem is working fine as well. Arris did have issues with the 6K series (Puma6) based chipset, but the 8200 has worked well with Comcast for me. Both IPv4 and IPv6. I'm using with Gigabit speed.
