cedric108

Thanks for the explanation about Hybrid VPN. Yeah, I remember seeing the patch notes mention that they were starting to crack down on VPN usage. It just wasn’t as strict back then as it seems to be now. Hopefully, they’re still testing different values and this isn’t the final setup. In the meantime, I can still play with my friend in Japan by connecting through the New York server. I also noticed that using a wired connection helps lower the ping a bit, sometimes enough also to get the DC server under the threshold too. I’m keeping an eye on the situation to see how it develops. And by the way, thanks for developing the geo-filter! Without it, I wouldn’t even be able to play with my friend, and we both get a solid experience because of it.

Same experience here. Something must’ve changed on Activision’s end. Do you also play outside your region with high ping? I use geo-filter to connect to US servers from Europe so I can play with a friend in Japan. It used to work fine, but ever since the update OP mentioned, I can’t find games anymore, unless I only include servers with latency under 100ms (New York server). I also tried the Saudi server (~90ms), and I’m able to find games there. If I stick to West Coast or Central US like I used to (130ms–180ms range), I can’t find any matches at all. Can the Hybrid VPN feature solve this issue? (Still not available on R3?) I am not very familiar with that. Would it be possible to just route my location data through Hybrid VPN, but perverse my raw connection for gameplay?

I have separate bands (no merging of 2.4GHz and 5GHz) on all firmware versions, including .540 and .290. I need more time to observe after downgrading, but .290 was the most stable version since launch of R3, zero issues until the latest update.

Hi Fraser, just let you know. I am also experiencing the same issue with the latest .540. I did a downgrade to .290, no more logs, but I can share my settings. 2.4GHz and 5GHz separated All smart features disabled (congestion control, smart boost, etc.) IPv6 disabled

I didn't disable the protection options, but somehow, the speed is back to 350-400 mbps on all my devices, still lower than the launch firmware's 600 mbps, but that's ok, consistency is more important. The only difference is this time I used R3's own power adapter, last time I borrowed XR1000's power adapter. Not sure if it is related.

DHCP without VLAN

I don't have an ISP router. My ISP allows me to use my own setup. I use a media converter (TP-Link MC220L), paired with a transceiver (TP-Link TL-SM321B), to convert my optical fiber signal to electrical signal for Ethernet. The media converter has an Ethernet output, my router (R3 or XR1000) is directly connected to this port.

Hello, By pre-patch, I meant 4.0.41 and earlier. I did use an analyzer to setup my test. R3 and XR1000 were tested with the same width, same channel, same location and same antenna orientation.

I am having the same issue. My post:

Hello, I set my XR1000 and R3 both in Router mode, I don’t have an ISP router.

Hello Netduma team, I recently updated my router with the latest firmware patch 4.0.219 and noticed my internet speed has dropped significantly. First off, thanks to the team for fixing a lot of bugs with this update, but now I’m experiencing this new issue. Ethernet -> OK R3 performs well, I got 900+ Mbps for both download and upload, this is indeed my internet speed. 5GHz WiFi -> Issue I’ve compared Post Patch R3 with my old XR1000. Pre Patch R3's data was obtained early this year. Conditions: Same channel, same width SmartBoost and congestion control disabled and enabled both tested, same result. Speedtest bypass on Both Mac and Windows tested, same behavior Results are consistent, I ran multiple tests. Tested at 2 am, no network traffic. All devices support WiFi 6. Speedtest performed using native apps and browsers, same result. Geofilter added, but off. Results (in Mbps): Windows machine -> Pre Patch R3: 600+ for both download and upload Post Patch R3: 130 download and 500+ upload XR1000: around 350 for both download and upload MacBook Pro -> Pre Patch R3: 500+ for both download and upload Post Patch R3: around 130 for both download and upload XR1000: again, around 350 for both download and upload Wireless Data Transfer between MacBook Pro and iPad Pro -> Pre Patch R3: bugged Post Patch R3: slow, macOS shows around 800 Mbps TX Rate. XR1000: 1700+ Mbps TX Rate. Gaming Impact -> Last night with Post Patch R3 (steady ping on), I got killed multiple times in COD after I run around a corner. I know this is an unavoidable lag issue for online gaming. My friends report it frequently, but maybe I am lucky, I have rarely encountered it myself. In fact, I don't even remember experiencing this problem in COD since 2007. No problem with Pre Patch R3, and no problem with XR1000 either. However, after applying the latest R3 patch, I'm now experiencing lag-related deaths 3-4 times in one night, which is highly unusual for me. Has anyone else experienced this? Any ideas on how to fix it? Thanks!

Are we getting a new firmware this month?

Hello Fraser, I have a question. I have no issues using Discord when Geo-Latency is disabled, am I doing anything wrong?

Thank you very much. I like being able to receive new firmwares regularly. The update process this time is much more smoother than previous firmwares. I am going to do some in-game tests. By the way, the issue where local wireless devices connected to the same Wi-Fi frequency (5GHz / 2.4GHz) can't communicate with each other has still not been fixed. Is this bug going to be fixed soon? Thanks.

Overall R3 works fine. Geo-Filter works. I am not experiencing those network connectivity and low download speed issues that others are reporting, expect a major issue I already reported. Wireless devices on the same Wi-Fi frequency cannot see each other, for example devices connected to 5GHz are all isolated, but they can communicate with devices connected 2.4GHz. It causes a lot of problems with smart home devices, printers and local file sharing.

Is the XR1000 more stable? I've come across some Reddit posts expressing concerns about the XR1000, particularly regarding QoS and Congestion Control. Personally, I don't need these two features. If the Geo-Filter and the router's basic features are stable and bug-free, I am also interested in temporarily switching to the XR1000. I will, of course, continue using the R3 in parallel and assist the ND team in improving the firmware.

Hello, I have a question. What’s the expected behavior of Geo-Latency Mode? I have been playing with Geo-Latency off since 4.0.20, after upgrading to .40, I want to do some tests. Let’s say I am from Europe, with Ping Assist off, Strict Mode on. If I put the filter circle in the US, am I going to only get US lobbies with Geo Latency on? If not, how does Geo Latency work?

Is 4.0.23 going to be released directly through dumaOS web/mobile interface?

It must be the issue of local wireless devices not being able to see each other on the same WiFi frequency. Netduma devs are aware of this issue. In the meantime, I recommend splitting the 2.4GHz and 5GHz WiFi frequencies. Place smart home devices on the 2.4GHz network or hardwire them to an Ethernet port, and use the 5GHz network for your main devices.

Yes, this was exactly what happened to me. Not very often, but it does happen. If it occurs, I have to either play with UK servers or stop using the geofilter for that evening (CET). It always returns to normal the next day. Weird issue, isn’t it? 😅

Yes, indeed. That's why 99% of the time, the authentication server is not even displayed on the geo-filter map. I wasn't aware there was always an authentication server. However, as my previous screenshots have shown, the authentication server can sometimes be displayed on the map. I still don't know what triggers this behavior, perhaps the game itself is bugged and mistakenly assumes that a connection to the London authentication server means the user can also be placed into London game servers. Based on my observations, things seem to return to normal after midnight CET.

I noticed that someone has revisited this topic. I want to share some new findings. I experienced this issue once again one week ago. It seems to be time-based. It occurred after 7 pm CET, and although I don't remember which day of the week, everything started working again after midnight, between 12 am and 1 am CET. 99% of the time, the authentication server is not explicitly displayed on the geo-filter map. However, if it is explicitly shown, it typically happens within a specific timeframe, disrupting the geo-filter.

Hello Fraser, just a quick question about the upcoming firmware. Does the firmware .23 fix the issue of local wireless devices not being able to see each other on the same WiFi frequency?

Thank you very much for the clarification. I am using version 4.0.21. Actually, everything is working fine today (no setting change, no reboot). It seems that if the authentication server is displayed on the GeoFilter map, the issue may occur, but if it's not explicitly displayed (which is usually the case), everything works as expected. I am going to keep monitoring the situation.

ok, I see. Thank you. Does having an authentication server outside the circle also disrupts GeoFilter on your side?