All Activity

Bnet has always been is for me. No pc not added to dmz. Nat type still shows as open in game. No port forwarding done. Cant i send the logs privately for all the data in them?

It seems as though technology is advancing very quickly. I am just trying to keep up. lol

I don't know specifically though with the features we're making e.g. ACC we wouldn't need it for that aspect at all. I suspect we would want/need better hardware if we were going to do things like this though as we push it to the hardware limits as is most of the time. Good suggestions though, I will pass it onto the team!

Hey Duma Army, I’ve been following the latest wave of Wi‑Fi 7 routers, and a lot of manufacturers are now integrating AI and machine‑learning capabilities directly into their hardware. For example, ASUS recently launched routers with built‑in NPUs (Neural Processing Units) that handle things like AI‑driven QoS, traffic optimization, latency reduction, smarter energy management, and enhanced security features such as ad and tracker blocking. There’s also industry discussion about how AI/LLMs could enable self‑optimizing networks, proactive troubleshooting, predictive failure alerts, and intelligent assistants for configuration and problem‑solving. These features don’t always require dedicated hardware — some implementations use hybrid approaches (local + cloud). Is it technically possible for future Netduma firmware to include any form of AI‑ or ML‑enhanced functionality? I’m thinking about features such as: Machine‑learning‑based congestion prediction Adaptive QoS that learns usage patterns over time AI‑driven traffic prioritization Smart security detection or anomaly monitoring Any kind of on‑device or cloud‑assisted AI logic I understand that full AI acceleration (like what NPU‑equipped routers get) may require hardware support, but I’m wondering if some level of ML‑based optimization could still be implemented on current or future DumaOS builds. Would love to hear from the devs or anyone familiar with the hardware constraints. Is this something that could realistically be added in the roadmap, or would it require next‑gen hardware? Thanks!

Have you changed the region on Battle.net? If it's set to Europe there and you're constantly trying to connect to the US it may not work. Have you put your PC in the DMZ or done any port forwarding? You can add the logs here

Click on the device you've added on the Geo-Filter then there will be an option to toggle off Filtering

When you say disable, do you mean just extend it so its not limited to the area I want? Unsure how to completely disable it

where can i attach the logs for you

canceling the game search

here is a video with the start up. london server did not lit up again. video.mp4

so i went down to 290 fw. Then upgraded to 540 from the popup notification. Set my geofilter strict mode to east coast. When starting up cod 2 dublin servers and one london popped up. once in the game lobby, 3 east coast servers lit up. I clicked on all 3 plus the initial 3 to allow. Search starts at 90ms and climbs to 110ms without getting into a game for about 10 min. The only servers that are now showing are the ones in Dublin and the london one from the initial start. Nothing ion the us

But what about when you're specifically in the game playing/just before it, do you see two within the radius - don't include Ireland in your radius, as you've allowed them they don't need to be there but it will help narrow down if there is one that has been missed there

yes when the game is loading i can see 2 dublin, one london, one washington and one las vegas. Thats even with geofilter set in uk. But most of the time the 2 dublin ones show up even before searching for a game. these are allowed ever since you mentioned it.

So there is likely a server within your UK radius that needs to be allowed that isn't - are you seeing two icons when playing a game within the UK radius?

Just to add. If i set the geofilter on uk only i do get games. Same as extending the geofilter all over Europe. But if i move it anywhere else and uk is not part of it nothing. Just like the spain example

Yes i did try the fixes. No changes have been made ever since i have bought the router. It was set and forget. The changes started with the new fw when i first replied to the post that it stopped connecting to the us servers. Like i said previously i have never had to allow any servers or change anything. All i have done is disable the WiFi as I only use it wired for the gaming pc. All the settings stayed as they were. No ping assist, strict search on. Set the radius and played like that for nearly what now 2 years or since the new router launched, forgot the time

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?

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

Ahh good to hear, thanks for the update!

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 !