NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
cybot
Jul 06, 2021Luminary
R8000p IPv6 6to4 DNS broken
-Firmware Version V1.4.1.68_1.3.28 for quite some time now, the DNS of the IPv6 6to4 setting has been broken. the issue goes back at least several firmware versions. you cannot enter any DNS set...
cybot
Oct 19, 2021Luminary
A security Hotfix firmware (V1.4.1.82_1.3.40) was released that fixed the issue. IT fixed two issues I was having and introduced two new ones. LOL
- FURRYe38Oct 19, 2021Guru - Experienced User
Well mark this thread as solved if it resolve the initial problem.
What other problems did it it seem to introduce?
Did you factory reset and setup from scratch after the FW update?
- cybotOct 19, 2021Luminary
immediately following the upgrade to the firmware, the wifi (all three bands) would suddenly disappear momentarily like the router was rebooting (it wasn't - or should not have been) and then reappear several seconds later. this would of course result in momentary loss of internet for all devices. the other issue is that the 2Ghz band network is not working properly and won't allow any devices to logon to the network. the password is correct, and the network info is correct, and the dual band devices are able to log on to the 5Ghz network, but the 2Ghz network is failing to be connected to. windows says: "couldn't connect to this network" and my pixel 3a XL phone connects to it, then disconnects to it.
I was able to get this error from windows event logs: Initialization failed because the driver device could not be created. Use the string "8EC4446365CC" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name.
but since no other devices can connect to is either, it is not something with windows or the device drivers
and yes. I did a factory reset before AND after I upgraded to the new firmware
- FURRYe38Oct 19, 2021Guru - Experienced User
Something to let NG support know about then...