NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
NotDJK
Oct 29, 2021Aspirant
Bug in R800P firmware v1.4.2.84_1.3.4?
Spent a lot of time troubleshooting this in the last two days, hopefully I can get some confirmation that I'm not losing my mind. Relevant network setup: Nighthawk R800P as my primary router (WAN ...
FURRYe38
Oct 29, 2021Guru - Experienced User
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Have you connected the xbox consoles directly to the router to see if problem still continues?
Does this still happen with the WAX206 turned OFF?
Has a factory reset and setup from scratch been performed since last FW update then try to replicate the issue?
- NotDJKOct 29, 2021Aspirant
I think my assumptions are wrong. After posting my message, I again saw the behavior on the Xbox Series X (downstairs wired to the WAX206). More interestingly, right now on the Xbox Series S wired to the R8000P, I'm seeing that NAT is now at STRICT and UPNP not successful. First time I've seen this message, so I'm kind of stuck, but thinking that it's actually an issue with having two Xbox consoles on the same network.
I should have mentioned in the beginning that the Series S is new to the network, added on the same day as when I did the firmware updates. I thought the problem was with a bad update, but now I don't think so.To respond to your specific questions:
- ISP modem: xfinity, XB7-CM
- the Series S is directly connected to the R8000P
- the Series X is directly connected to the WAX206
- I have NOT tried connecting both to a single device, just didn't want to pull everything apart when it didn't seem a likely issue
- Yes, it happened with the WAX206 OFF, which would mean it occurred at a time when the Nighthawk was the only router on the network and the Series S the only console on the network. NOTE: this is why I wasn't originally thinking that two consoles on the same network was an issue.
- I have NOT done a factory refresh of the R8000P. I did the firmware revert, a firmware current, and then a firmware revert as part of testing, but never a factory refresh. I figured the firmware update covered the factory refresh, but maybe I'm wrong?
I am really lost here. I don't mess around with the network device settings so I don't know if I should be setting up static IP, port forwarding or anything else to help. I wouldn't even know how to do this if it was recommended. I also want to get my R8000P on latest firmware if this issue isn't a bug, but haven't updated yet until I can sort the overall problem out.
Any guidance you might have would be extremely appreciated!
- FURRYe38Oct 29, 2021Guru - Experienced User
"xfinity, XB7-CM" this already has a built in router and wifi. This would be a double NAT condition which isn't recommended. Especially for game consoles.
https://kb.netgear.com/30186/What-is-Double-NAT
https://kb.netgear.com/30187/How-to-fix-issues-with-Double-NAT
Couple of options,
1. Configure the modem for transparent bridge or modem only mode. Then use the NG router in router mode. You'll need to contact the ISP for help and information in regards to the modem being bridged correctly.
2. If you can't bridge the modem, disable ALL wifi radios on the modem, configure the modems DMZ/ExposedHost or IP Pass-Through for the IP address the NG router gets from the modem.Also you might set NAT FIlter to OPEN under Advanced Tab/Settings/WAN setup...
- NotDJKOct 29, 2021Aspirant
Thanks for the quick reply!
- I already have the xfinity modem in Bridge mode. Solved the double NAT issue as soon as I had the new modem in place many months ago :)
- I actually found this comment on reddit while searching for R8000P and two Xbox consoles, thinking that UPNP was a problem:
"On a relevant note, to get the R7000 working with multiple X1's (open NAT on both) you have to change a particular setting on the router itself. This is probably applicable to the R8000 as well. Remove any port forwards and disable triggering. Turn on UPnP Then go to advanced -> setup -> wan check disable sip alg and check open instead of secured Reset the boxes."
As it happens, on my device I don't have any port forwards in place, and port triggering isn't enabled as far as I can tell. But, I did see that for NAT filtering, Disable SIP ALG was not checked, and Secured was selected instead of Open. I assume this is what you are referring to in your comment. I don't know what SIP ALG means, but I've disabled it, selected open, and will now run some tests.