Netduma Fraser

Routers are designed to be online all the time and so I don't think there is anything we can do currently to resolve it, if you keep turning it off you'll have to keep re-enabling it. We can look at trying to reconnect it automatically in a future update.

No currently you can only use OpenVPN or Wireguard

As the game was already on the game had already determined you could connect to all the servers hence when you turned it on those connections were already active and therefore not blocked. You need to have the Filter enabled before you start up the game, then it will work. Close the game, enable filtering mode, wait 2 minutes then launch and it will block correctly.

Not optimally no, as above we need to do a bit of work to get it working, unlike other games that may just require a cloud update

It is a misreading then caused by the Geo-Filter. It will actually be Open when the Geo-Filter is enabled so you can ignore it.

Are you checking NAT on the game? Sometimes the Geo-Filter can cause a misreading so that is likely what is happening if console NAT reads Type 2

Yeah they basically prevented any sort of Geo-Filtering, they made a big post on it on halowaypoint a few months ago so we're seeing if there is anything we can do.

You have the filter disabled, you need to enable Filtering Mode in order to filter correctly.

It's still not working properly with the Geo-Filter but we are still looking at potential workarounds

Ping Assist doesn't work as well with Destiny, try just using the radius instead, if that isn't working please include a screenshot of the Geo-Filter page of how it is set showing what you see when trying to get a game.

It should work getting a close server, this guide should help: http://support.netduma.com/en/support/solutions/articles/16000077072-dumaos-optimal-settings-guide-geo-filter

Ces détails n'auraient pas vraiment d'importance en ce qui concerne la configuration du réseau, il serait simplement important que tous les appareils soient connectés au R2 ou derrière, mais je vais obtenir les informations pour vous.

Je devrai demander à un développeur si vous voulez ces détails spécifiques, y a-t-il un cas d'utilisation pour avoir besoin de connaître ces détails ?

Are you rebooting the router a lot? Set a static/reserved IP for the XR on the modem so it doesn't change, then put that in the DMZ and you should be good.

Ahh so you did an actual Traffic Controller rule and allowed ALL traffic to the console I presume? Yes that would create a conflict, it's also not necessary to do that rule, it doesn't create any sort of priority, that is what Traffic Prioritization on the QoS page is for. Well done for resolving the issue.

Do this again: Quit the application/game/client/turn off console completely Remove device from the Geo-Filter Resync from the Geo-Filter Map menu Re-add the device to the Geo-Filter Set up the Geo-Filter how you like Wait 2 minutes Boot up console then application/game/client Then see if it works.

The WAN Setup is fine, did changing that option give you an Open NAT? What is the Samsung device that you have added to the Geo-Filter - the PS5? Also there would just be one server in that radius and it doesn't always seem to be available so you will struggle to find a game.

Can you provide a screenshot of the entire Geo-Filter page please?

Where are you checking the NAT? Set it to Open in WAN Settings

It applies to the entire device, no ports are needed

The console will add automatically and be greyed out, it will apply to the whole device so you don't have to add ports

Are you just trying to filter to get a close server or are you trying to match solo or against friends?

The link above covers progress for all the platforms

This is something we're aware of, the Geo-Filter currently doesn't work properly with the game due to this and it's something we're investigating.

¿Qué error ves al habilitar/deshabilitar? Si deshabilitó DumaOS Classified Games cuando ya estaba priorizando, entonces tendría que cerrar completamente el juego/cliente del juego y luego de unos minutos se detendrá y se deshabilitará por completo. Un restablecimiento de fábrica desde la interfaz debería ser suficiente.