NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New - R7900P/R7960P/R8000P Firmware Version 1.4.3.88 Released
Security Fixes: 04/13/2022
Fixes security vulnerabilities.
For more information about security vulnerabilities, visit https://www.netgear.com/about/security
Download Link:
R7900P:
...
Be sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/24231/How-do-I-back-up-the-router-configuration-settings-on-my-Nighthawk-router
Jimsto2 wrote:
Ok folks, I finally got back to working tis issue. Before trying a full factory reset, I enabled IPv6, rebooted the router and the devices. That appears to have corrected the problem. I have not gotten a DNS error since. Thanks for the assistance. I'll update if it shows up again.
All,
I have read several posts about DNS not resolving and am suffereing the same issue and it is now impeding my ability to work from home. I can tell you the following:
- I used a managed switch and wireshark to monitor the traffic between the R8000 router and my cable modem
- I also used a seperate wireshark to monitor traffic between my laptop to the R8000 router
- I can see my l laptop send a DNS request to the router and the router forwarding the request to the specificed DNS service on the public side of the network. I also note the UDP source port on the public DNS request so I can then match it to my laptop request given the NAT table changes this.
- I can see the DNS service send a valid response back to the R8000 router with a destination address of my public IP address and the approprate destination port with matches the port used for the routers DNS request.
So far, so good, everything is as expected. Now it gets wired:
- The R8000 sends my laptop a DNS response with a "REFUSED" response code. Note, the DNS response from the DNS service did not have a REFUSED response code and in fact has the resolved address in it.
- The R8000 also sends the DNS service an ICMP message "Destination Port Unreachable". Funny thing is it I can see it is the correct desination port.
Clearly, this is not the correct behavior. It has nothing to do with my ISP or anything else like it.
Also, when I filter the trace on the public-side for ICMP Desination Port Unreachable messages, I have a lot of them and they are all comming from the R8000 and they are all assocated with DNS server responses.
I have the traces if it helps. I would like to know when there will be software to fix this, what work arounds are available, and if there is an older firmware version the WILL WORK.