BO7 won't load

[Netduma Fraser]

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

[qwerty0776]

more east coast id in this short video. Yeah is refusing to let me in a game. Keeps trying but 'gives up' really fast.

[qwerty0776]

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

[qwerty0776]

[qwerty0776]

trying to look for a game again more ID's

[Netduma Fraser]

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

[qwerty0776]

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

[Netduma Fraser]

40 minutes ago, qwerty0776 said:

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

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

[qwerty0776]

15 hours ago, Netduma Fraser said:

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

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

[qwerty0776]

As a test i tried closer. Same issue

[qwerty0776]

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:

1.  

   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

    

2. 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

    

3.  

   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. 

[qwerty0776]

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:

1. 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.

    

2. Increase Distance: Increase your Geo-Filter distance to at least 2500km+ to ensure US coastal servers are captured.

3. 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.

[qwerty0776]

Btw i ised  my vpn just for testing and it did connect me to a game so f that helps

[Netduma Fraser]

If you disable filtering so you can still see servers on the Geo-Filter do you get a game anywhere without an extended search? Did you make any settings changes or physical setup changes around that time? The test closer the server you tried to force is a server that doesn't always seem available, that and the Italian server, see if you can force a different one in the EU.

You've not provided us any logs so I can't really comment on the AI summaries but did you try the 'fixes' it suggested?