All Activity

Comparing the two sets of logs, the second log file (ending in 45.075Z) reveals the specific configuration error that is preventing you from reaching US servers. 1. Incorrect Home Coordinates (The "Australian" Problem) The most significant issue is that your router's "Home" location is set incorrectly in the background, even if the interface shows the US. The Error: The log explicitly states: Home coordinate set to (-33,143). The Consequence: These coordinates are for New South Wales, Australia, not the United States. Because the Geo-Filter calculates distance from your "Home," it thinks you are in Australia. Even if you set the filter to the US, the massive distance between Australia and the US likely exceeds your allowed range or causes the filter to malfunction. 2. Extremely Low Distance Range The Error: The second log shows the Distance set to 786. The Consequence: A range of only 786km (roughly 488 miles) is very small. If the router believes you are in Australia, it is looking for servers within a 786km radius of New South Wales. No US servers will ever fall into this tiny circle around an Australian coordinate. 3. Missing System Files The second log shows a critical error that was not as prominent in the first: The Error: [ERROR]: dlopen(): geolatency.so: cannot open shared object file: No such file or directory. The Consequence: The geolatency.so file is essential for the Geo-Filter to measure the distance and ping to servers. Because this file is missing or cannot be opened, the Geo-Filter "engine" is likely running in a broken state, failing to correctly identify or allow US-based server pings. 4. Continued Service Instability Both logs show that core services are struggling: UPnP Failures: The miniupnpd service is still failing to send packets, which will cause NAT issues . +1 Websocket Errors: The Ping Heatmap tool is failing with address already in use errors, meaning it cannot accurately show you where the best servers are. Recommended Fix: To resolve this, you need to force the router to update your Home location and fix the missing file error: Hard Reset Home Location: In the Geo-Filter settings, manually move your "Home" pin to a completely different continent, save it, and then move it back to your actual location in the US and save again. This should overwrite the (-33,143) coordinate found in the logs. Increase Distance: Increase your Geo-Filter distance to at least 2500km+ to ensure US coastal servers are captured. Check for Firmware Updates: Because the logs show a "missing shared object file" (geolatency.so), your firmware may be corrupted. Re-installing the current firmware or updating to a newer version is necessary to restore that file.

also closer same issue from the logs: Even if your Geo-Filter is set to the US, the logs reveal several critical system errors that are preventing your router from establishing those connections. Based on the logs, here is why you are still being blocked: UPnP Failures: The miniupnpd service (responsible for opening the ports required for gaming) is failing completely. It is reporting "Cannot assign requested address" and "try_sendto failed to send" errors for numerous packets. Without working UPnP, your NAT type will likely be "Strict" or "Moderate," which prevents you from connecting to remote US servers regardless of your Geo-Filter settings. +4 DNS Rebinding Protection: The logs show that "DNS rebinding protection is active," and the router is explicitly "discarding upstream RFC1918 responses". This can cause the router to block the very addresses needed to resolve and connect to US game servers. Module Initialization Issues: Multiple services are failing to start correctly. Specifically, there are repeated errors stating the system "Failed to look up com.netdumasoftware.hybridvpn object". Even if you aren't using a VPN, the failure of this core component can cause cascading issues with how the router handles traffic routing and filtering. +4 Crash Loops: The cgi-runner instance is in a "crash loop" (6 crashes recorded in the logs). This service is vital for the DumaOS interface and background tasks to function. If it is crashing, your Geo-Filter settings may not be applying correctly in the background even if they look right on your screen. +2 Recommended Fixes: Reboot the Router: Since multiple services (UPnP, CGI-runner, and Hybrid VPN) are in a failed state or crash loop, a full power cycle is necessary to restart these modules. +3 Toggle the Geo-Filter: Disable the Geo-Filter entirely, wait 30 seconds, and then re-enable it. This can sometimes force the background "geoip-daemon" to reload its configuration. +1 Check for an "Open" NAT: If your NAT is not "Open" after a reboot, you may need to manually forward the ports for your specific game, as the logs show UPnP is currently unreliable. +1 Never had to do any of this ever since i bought the router when it came out.

As a test i tried closer. Same issue

I understand that part. However I don’t understand what changed since it was working just fine up until January ish.

Turns out it was Adaptive QoS > QoS in the asus, turned that off and get full speeds. Xbox is now full speed. But PC, I think I've broken my network port some how as its dropped to 40MB, put a in usb adaptor and get full speeds.

Pour un usage domestique avec une ligne inférieure au 1Gps les routeurs Netduma font très bien le travail et vous propose des fonctionnalités innovantes par rapport à la concurrence. Les seules points qui pourraient être améliorés seraient la portée du Wifi et un commutateur intégré multi-Gig Points facile à anticiper avec un commutateur externe et une AP … Du point de vu rapport qualité/prix le logiciel Netduma plug and play surpasse tout les autres !

You may be connecting to closer servers and those players are connecting to the same servers, there is nothing that would prevent them doing that. The servers could be under load which would account for the higher ping. You can try filtering with it and it may work, I just wouldn't expect it to work 100% of the time. We have been looking into a solution for it which would require an update to the Geo-Filter functionality itself so it is a possibility we're working on.

even tho you can select region like europe it still connects me to mostly russians and arabs language wise and my ping skyrockets compared to the servers where i do belong which is center of the most servers available, the netherlands, literally so many servers around me in a 30ms radius yet the matchmaking is so strict it just puts me miles away because of toxic lobbies, such a shame geo filter doesn't work. poopy feels like a shadowban because of the extremely strict matchmaking like skill/aggression/interaction/communication everything any idea if you guys will ever find a way to get geo filter working on games like arc raiders?

I'll give it a few days as it is a brand new line

Yeah that's a less than useful answer, clearly didn't read it properly. It's possible they didn't update it correctly but also if this is a new upgrade then it can take some time to settle, in which case you may just see the guaranteed speeds for a few days/weeks and then it'll start to improve. Probably best to give them a call to determine exactly what is happening.

Likely because it thinks the TV is the console and you've added the device you think the console is to the Geo-Filter. Check the IP of the console on the device itself then check the IP on the Device Manager and match up the devices, rename if necessary then re-add it to the Geo-Filter.

If the Geo-Filter is preventing servers outside your radius then it's doing its job, if the game doesn't let you in then we can't really do anything - it also isn't the purpose of the feature to force servers that far away. That's unlikely to help but you can give it a try

So that test was done with in my Asus routers software, so I'm "guessing" the connection is syncing at 500MB, when it should be 900mb, the guaranteed being 500mb. But if I do a speed test via wifi on the ASUS I'm only getting 250mb. I've not got a long cable or any thing like a laptop to get by the router enough to test yet. Kinda thinking I've been put on the wrong profile for what I ordered. So asked the question on plusnet forums and get this as an answer, helpful...

I play Battlefield 6 on PlayStation 5, not on LG which is my TV lol,and why is it inactive

yeah still not working. should downgrade to a different fw? older maybe?

We just need the IDs for the authentication servers, we can't do anything with those US ones if they're in the correct place

trying to look for a game again more ID's starting game.mp4

private match servers if helps. i can star a game there with my old ping 89 ms p[rivate match.mp4

more east coast id in this short video. Yeah is refusing to let me in a game. Keeps trying but 'gives up' really fast. Recording 2026-02-28 184244.mp4

Thanks for the IDs, I'll pass them onto the team

I think I know who you mean! I do get you and I would like some more focus on that too. What are the issues you're having specifically?

No nothing else specifically. Okay that's good, it's preventing you getting into a game outside properly. Now you're running into what can happen which is increased search times when forcing servers further away. Depending on when you play the game may also be less lenient about allowing you in.

fresh setup- is attempting to connect for about 10 mins now. Geo latency off, filtering enabled 2nd pic