Jump to content

Recommended Posts

Posted

I’m having an issue where the Geo-Filter on my Netduma router does not consistently apply to both of my consoles.

Here is what’s happening:

• Both consoles appear in Device Manager correctly, but on the Geo-Filter page, they constantly switch between “Inactive” and “Waiting for host.”
• Only one of the consoles ever actually respects the Geo-Filter radius.
• The second console ignores the filter completely and still connects to my normal closest server, outside my set radius.
• Sometimes neither console applies the filter at all — they both stay “Inactive” even while searching for a match.
• When I try searching for a game on the console that isn’t being filtered, Geo-Filter immediately flips to “Inactive → Waiting for host → Inactive” on repeat.
• Even loading into a game manually doesn’t activate the filter; it continues to show as Inactive.

What I’ve already done:

• Rebooted consoles, router, and modem
• Re-added both consoles to the Geo-Filter
• Tried Filtering Mode on and off
• Verified both consoles are showing as connected devices
• Confirmed that only one console ever triggers the Geo-Filter while the other bypasses it

It looks like the Netduma is only routing one console through the Geo-Filter correctly, while the other console is bypassing it and going straight to the closest server.

Any suggestions on how to fix this would be appreciated.

  • Administrators
Posted

I've responded to your email, we can continue there, we don't chat over Discord/phone for tech support

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...