Netduma Liam

Great, thanks for that. So could you now please go to Settings -> WAN Setup -> Set NAT filtering to Open. Check if you're still having NAT issues after this.

Thanks for the information! I've passed your feedback so far on to the team and we'll see if we can recreate the issues you've experienced. In the mean time, try accessing the interface to make changes in either Chrome or Firefox, we've heard of a few visual issues in Edge and we're working on fixing that. While these likely aren't the cause of the issues you're having, it won't help. As your modem is a pure modem and not a router/modem combo, presumably your XR1000 has an external WAN IP, correct? That being the case, it's strange you're having NAT issues at all. Are you able to provide some more insight in to your exact physical setup? As I currently understand, it's simply Modem -> XR1000 -> Connected devices. Is that right?

So it didn't let you in to the game right? It booted you back to menu? I think that's the current behaviour we've found in our testing too. We're looking into the possibility of makes Geo-filter's blocking a little more gentle so games don't react in this way, but I don't have an ETA as to when we might be able to make those changes.

What was going on in-game when you took this video? It shows it as being blocked so you shouldn't have gotten into a game, though I don't have Battlefield yet so I haven't tested it myself. Are you using a VPN at all? It's weird that it'd try connect you to a server so far away.

Yeah Netgear are well aware of this one, it will be resolved for the next firmware.

Can you share a screeenshot of your Geo-filter setup? It should be working nicely so perhaps we need to optimise your config a little more.

We haven't been able to recreate the port forwarding issue, hence why we asked for some more detail on it as it's not a problem we've heard of before. Same applies to the question on restoring from backup, we need to know what you're expecting to be backed up and what the symptoms of the problem are before we can try to reproduce your exact issue. I assume Fraser's explanation on Traffic Prio has answered your original question.

I'm not suggesting you put the console in the DMZ, I agree that's not secure. Put the XR1000 in the DMZ of the ISP router, that will solve any NAT issue while still being secure. Can you send a screenshot of your custom traffic prio rules so we can take a look at what might be the issue?

Netgear are aware of the issue with UPNP, as a workaround I'd suggest putting the XR1000 in the DMZ of the upstream router so you don't have any NAT problems. Make sure you remove all port forwarding rules when you do this. What is indicating to you that Traffic Prioritisation isn't prioritising TCP packets? Are you using a custom rule you configured yourself or are you using the DumaOS classified games rule?

3.0 n'est pas en version bêta sur le R1, il est entièrement publié. Nous publierons bientôt une autre mise à jour avec les derniers changements.

Cela arrivera une fois que nous aurons publié le firmware R2, après quoi nous porterons les mêmes modifications mais quelques modifications spécifiques à R1 sur le R1 et publierons un firmware pour cela.

Sure! Assuming we can capture it OK, it should be on Ping Heatmap later today.

OK, thanks for letting us know, we've got a new firmware coming out very soon for the R2 so that should definitely help with the problem!

OK, glad to hear it was able to get through the boot process properly then. I believe it's more a case of residual power draining rather than heat, although it's never a bad idea to give it a little more ventilation! Let us know if you run into any other problems with it.

OK, thank you. Could you please try Fraser's last suggestion and see if that helps?

I can certainly understand your frustration, we understand that screenshotting your config isn't a feasible solution, more just a suggestion to help a user in the meantime. I'll also raise the problem with the team again to bring it to the forefront, I'll get someone to replicate it and investigate why it occurs from a backend perspective.

You can save device information and restore that on the R2, there isn't currently a way to save and restore network configuration however. I've responded to your post in the other topic, though if you'd like to troubleshoot the issues you're having it may be best to open a new topic.

To clarify, are you experiencing this on an R2 or on an XR500? What firmware version are you currently running?

Not sure, we found a bug while testing it so the devs are currently working on fixing that now. Once that's done we'll re-test it. After that, it'll go out to beta testers first before we can fully release it.

Righto, let us know if you run into similar problems again!

Were you able to get a recording of this? Are you able to provide the ID of the peer?

Cool idea! In the mean time you could probably just unplug the WAN cable and reconnect it again? Unfortunately there isn't a bridge mode currently available on the R2.

We've been working super hard and are now testing new firmware, it shouldn't be too much longer before we can release one!

It's not possible currently I'm afraid, what's the reason for needing to do this?

You can either check the R1 Support forum, or eventually we'll also put it on our Latest Firmwares page once it's full release. http://support.netduma.com/support/solutions/articles/16000091217-latest-firmwares