Netduma Liam

No worries, I've responded.

OK, in which case my next suggestion would be to experiment with forcing a few different servers, perhaps on a slightly higher ping around 30-40ms. I'm not sure what Halo do with Lag Compensation, but I know this is an issue in some other games so it's worth trying.

That's not the server you're playing on, that server is whitelisted for NAT purposes on Xbox. It won't affect your ping, don't worry. The server you're actually playing on is miscategorised as a peer, in the UK. You can tell this is the server you're playing on because the icon is much bigger than the whitelisted server in the US. Can you check the Network Statistics in the Settings Menu on Halo next time you're in a bad game and check what ping it says you're getting?

OK, I'll use the information you've provided already to double check if we've got it whitelisted anywhere. Let me know once you've got some screenshots, it would be handy to see the information shown in auto-ping host trdonorthcentralusx1vmss.ipv6.microsoft.com.akadns.net

Fraser will be back tomorrow afternoon, if it's urgent you can DM me.

That's really odd, what firmware version are you currently running on your R2? Does the US server show as being allowed in Geo-filter or does it still show a blocked icon? Can you provide a screenshot of the issue you're seeing with the allow and deny panel?

It's something we can do without needing to release a new firmware, so hopefully soon. The team member who looks after this will be back in the office this week so he should be able to update it then, provided it doesn't require any developer input.

Did you factory reset again after installing the firmware? Are you still able to access the interface when this occurs and if so can you grab a log file?

We're still working on improving how Geo-filter and Ping Heatmap work with Battlefield. What about Geo-filter doesn't seem to be working for you? How do you currently have it configured?

Sorry to hear that, please let us know how you get on with that.

Sure, or just change it to Console, whichever you like.

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.

Welcome to the forum! Geo-filter works with Halo Inifinite, we just haven't been able to add a profile for it yet. If you're on Console, just select 'choose manually' when adding your device to Geo-filter. If you're on PC, you'll need to change the PCs device type to 'Playstation' in Device Manager, then re-add is to Geo-filter using the above method.

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!