Netduma Liam

You can do that, however the QoS feature won't work nearly as well as if you had all devices going through the R2.

Since doing the upgrade, can you please factory reset the XR700 again and see if you can access DumaOS after that?

Welcome to the forum! Filtering only works when you are the host of the party. If you allow a connection while playing, the next time you try to connect to that person or server, they will always be allowed regardless of whether they're inside your filter radius or not. So for the problem you mention, you'll need to make sure you're the host of the party.

If your R2 gets an IP from your ISP router/modem, you'll need to give the R2 a static IP from your ISP router/modems admin interface.

¿Tienes problemas de NAT en el juego? ¿El R2 se conecta a un módem puro oa una combinación de enrutador/módem?

Interesting, thanks for letting us know. We'll see if we can replicate that and get it fixed!

OK sure, thanks. Any changes we can make to DHCP would have to come in the form of a new firmware, so it's not something we can hotfix for you now. You could perhaps try going back to them saying we're looking into their feedback but it would help alleviate the problem for the time being if they could extend your lease?

Where did you get that config file from exactly? I didn't think NordVPN supported WireGuard just yet. Realistically it shouldn't make a difference, but remove the comment in the first line please, just to be sure.

Yes, though you shouldn't need to do this more than once or twice!

Can you check the Xbox's device type in Device Manager? Is it set to 'Console' or 'Xbox'? If not, what's it set to?

Hey, I'll answer in order: If the R2 connects to the AX3000 for internet, connect it to the Blue WAN port. If the mesh is below the R2 in the network and the mesh gets it's internet from the R2, connect it to the yellow LAN port That sounds like the WAN IP of the R2, the interface is not accessible from here. You'll need to connect a device directly to the R2 and go to 192.168.77.1 in your web browser. You shouldn't need to make any networking changes to the R2, if it's all using DHCP it'll figure everything out itself. Yes, PS5 direct to the R2.

Avez-vous téléchargé le fichier de configuration OpenVPN depuis Express VPN ? Si c'est le cas, copiez tout son contenu et collez-le dans le champ de configuration. Ensuite, copiez votre nom d'utilisateur et votre mot de passe VPN depuis Express VPN et collez-les dans un bloc-notes. Supprimez tous les espaces de début ou de fin du nom d'utilisateur et du mot de passe, puis collez-les dans les champs correspondants de la page VPN hybride. Après cela, il devrait se connecter correctement.

Thanks for sending this over, I'll forward this onto the team and get them too look into this! Were the able to extend your lease anyway? Or have they not done that since finding this in the packet capture.

You're likely only able to connect to one server in that polygon, so if that server is too busy or down for maintenance, you won't be able to connect. Ideally set a couple more polygons over a few more servers for a more consistent experience.

Can you drop download more, to around 70%? Can you also watch Network Monitor when you're playing and see if it's purely detecting CoD, or if it's detecting any other games at the same time?

That's frustrating, do you still use the XR500 for anything else? Perhaps you could try connecting the XR500 to the R2, then put it into AP mode from it's settings. If you then connect devices to the AP, check if you get the Wi-Fi speeds you'd expect?

Do you use Geo-filter? Is that still working? Are you still seeing icons on the map when playing? If not, that could be an indicator to our problem.

OK good, yeah that's correct.

Do you know which firmware version you're running? I'd suggest making sure you're upgraded to the latest firmware linked below and make sure you've factory reset the R2 after installing the latest firmware.

Please, yes.

Can you expand your search radius more to include more servers and see if it's working better then? Your current radius is very small so you may struggle.

We will occasionally, if we have a new version with new DumaOS changes and we want to get it to some people before it goes full release, though at the moment we don't have any firmwares that are at this stage.

I suspect that may be the case, you could try manually allowing these, which will work eventually if they're just servers misclassified as peers. However if they're actual players and they throw this error when you block connecting to another player, there's not much you can do about that.

Since making the DHCP changes, do you have access to the DumaOS interface when the connection drops? Can you get to the URL http://192.168.1.1/debug.html during this time? If so can you grab a log from there?

Totally understand your guys feedback, we felt confident with the last firmware we tested that we would start giving it out before Christmas. Upon receiving a firmware with remaining bug fixes, there were some regressions. We've since fixed those and are testing those fixes as I write this. If the next firmware comes back with all these changes implemented and regressions fixed, I feel a release before Christmas is likely, however as you say, there's no way I can guarantee that.