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.
