All Activity

It only applies to new routers so the routers you already own will not be affected. In addition, we're not the manufacturers and so I'm sure that they themselves will apply for any permits that are required to continue being able to produce routers outside the US.

Hi, Any plans to circumvent the new restrictions, primarily firmware updates?

I've mentioned it a few times but we've been working on some big features which has caused delays with updates and not just for the R2. When the R2 was released it came with DumaOS 3, we never indicated at the time that meant it would get full compatibility with the next iteration of DumaOS but we're doing our best to give you what we can of it considering DumaOS 4 was developed on the R3 and the R2 hardware is significantly less powerful than the R3. I understand it's frustrating but it's likely the next update for the R2 will be the last so we need to ensure we get it right. NTGR mark their routers as End of Service when they feel the need to do so, there is nothing we can do about that unfortunately and we don't get 100% of those routers cost to continue development like we do with our own.

Great to hear, thanks for the update! That's really personal preference, it depends how much you want it to be prioritized over other devices, 5 will give it top priority overall

It's been a year and eight months since testing started, on the R2 and I'm wondering what you're planning to do. It seems like these guys might not be willing to help out. As a long-time customer, I've noticed a big change in the company's attitude. It looks like they might not be putting customers first anymore. This whole situation is pretty upsetting and disappointing. And remember that Netgear integration they told us was going to be the best thing ever? Well, now they don't even support it at all. They basically made you waste your money and time, and they're not even saying sorry for it. I'd tell everyone to download OpenWRT and get a mini PC; it does so much more than this Netduma ever will. Check it out, you won't be disappointed, and you'll have a lot of support from others on the forum.

I’d cap my bandwidth a bit below my actual line speed and keep QoS always on. I’d also lock my game device to a fixed upload and download to stop the big spikes.

Hi Fraser, I hope you and your team are having a good week so far. I manage to set it up successfully and I’ve kept my open Nat type. I found 80 down and 90 up was sweet soft, giving a+ rating with zero up or down added lat on bufferbloat test (Fritzbox was a B). On my old isp I had to go down to 60 percent to get rid of bufferbloat. When boosting ps5 device.should I set it to level 2 or level 5?

Good to hear! You might just need to fine tune the Congestion Control a bit more and ensure SmartBOOST is triggering correctly when playing

Added

can i have access to r3 beta?

I've followed through with the setup you two have recommended me with a lot of testing and it seems like it was a local network problem not BT, however, I still get jitters whilst in games but it's fine and I'm scoring an A. I appreciate the help, it's helped out a lot. Regarding the removal of the bt hub, that's something I can't do. I live in an old flat/estate building so I'm on a DSL cable which that can't go into the R3, hopefully one day I move out I can get FTTP 😭

Best thing to do is check with filtering disabled, do you ever get that server? If not then it's likely not currently available. We can list all the servers with heatmap but it doesn't mean they're all available at once

I'm experiencing the same thing and I'm in the same region... I've completed your the recommendations several times. Quit the application/game/client completely - including the Battle.net client from the System Tray - important! Remove device from the Geo-Filter Give the PC the PlayStation Device Type in the Device Manager Resync from the Geo-Filter Map menu Re-add the device to the Geo-Filter Set up the Geo-Filter how you like Wait 2 minutes Boot up application/game/client I'm using a Netduma R3 with the latest version on DumaOS. Also I noticed this starting happening last week before season 3 was released.

Your Xfinity gateway provides WiFi is that correct? In which case you'll need to put it in bridge mode or put the R3 in its DMZ. Does that mean you have devices connected to the gateway still? Always, Auto or Low Latency for Congestion Control? You'll need to experiment with the percentage here to improve your bufferbloat results. Keep in mind if you have speed test bypass enabled here you'll need to disable it for the test to register better to your changes. SmartBOOST is set fine. For the Geo-Filter: Quit the application/game/client completely - including the Battle.net client from the System Tray - important! Remove device from the Geo-Filter Give the PC the PlayStation Device Type in the Device Manager Resync from the Geo-Filter Map menu Re-add the device to the Geo-Filter Set up the Geo-Filter how you like Wait 2 minutes Boot up application/game/client To force servers you need to do the following: It's essential the Geo-Filter is enabled before the game client (e.g. Steam etc) or the game have been launched. If you change Geo-Filter settings when you're on the game then you will need to restart the game for those changes to take effect, otherwise it will use the previous Geo-Filter settings and appear not to be working. For settings ensure Ping Assist and Geo-Latency are disabled in the Geo-Filter menu that can be found by clicking ⋮ in the top right hand corner of the page and go to Settings. Strict Mode should also be enabled, it is enabled by default so if you haven't disabled it you can ignore it. If you have disabled it or want to check it can be found in the same Settings menu as above or in Settings > Troubleshooting > Advanced > Developer Options depending on your firmware version. Fast Search should also be disabled which it is by default so can be ignored if you haven't changed it, otherwise this can be found in the same place.

I will try to answer this as smooth as possible well also looking for advice with setting. 1. I have the DumaR3 connected to my Xfinity CBR2 Gateway Modem. I believe I have all my traffic flowing correctly with that setup. 2. I only have my PC connected to the R3 via Ethernet with no other devices connected. 3. I pay for 1250down/300up and get about 1400 down and 310up. 4. I let the DumaR3 run the test for for speeds and it was accurate. 5. I have it congestion control set to advanced and have both down and up set to 90%. 6. For smart boost I literally just did my PC and the gaming category. I don’t know if that’s good or bad. 7. I play PC on battle.net via Ethernet. 8. For the geo filter I just used the “use my location” option and then put the radius to about 530 meters. It still won’t consistently connect me to that Chicago server and stabilize ping for some reason. Any help is much appreciated and if you need any fine tune settings from my side or anything specifics just let me know. Thank you so much!

What is the model of the modem/router the R3 is connected to and how have you set that to ensure all traffic flows to the R3? E.g R3 in its DMZ, modem/bridge mode Are ALL devices connected to the R3? What are the speeds you pay for/receive? Have you entered those speeds into the router? How have you setup Congestion Control? How have you setup SmartBOOST? What platform are you playing on and how is it connected, via ethernet or WiFi? How have you setup the Geo-Filter?

Hello! Having some trouble connecting to my Chicago server (local) for COD Bo7. Also need help in getting an A+ on bufferbloat without totally destroying my download and upload speeds. Thanks.

Up to you, but If all devices are sitting behind the R3... You could remove the BT Smart Hub from the equation i.e. WAN line directly into the R3 and pop in the PPPoE creds. That's what I do with my BT/EE connection. See what works better for you hit reg wise (i.e. BT homehub handling the WAN or the R3)

Glad you found a workaround. It's not recommended to play with a VPN though as you will have a higher ping.

For the older games they do tend to start reducing the amount of servers available so that's likely what is happening here. If the Geo-Filter doesn't see them then they're not actively available unfortunately

Nvm found a different way to connect sending VPN to PC then console via USB Ethernet adapter.

HI Frasser, I still can't see the Amsterdam servers on Cold War and mw2023. I tried everything you have mention above. the only server that I see and connect are Frankfurt London and Paris.

Trying to use vpn with netduma while in game menu trying to connect it says Unable to connect to host. When i use Openvpn software shared network to ps5 it works. Hybird Vpn Config- Open VPN Using - client dev tun proto udp remote 217.138.208.91 1194 resolv-retry infinite remote-random nobind tun-mtu 1500 tun-mtu-extra 32 mssfix 1450 persist-key persist-tun ping 15 ping-restart 0 ping-timer-rem reneg-sec 0 comp-lzo no verify-x509-name CN=us9330.nordvpn.com remote-cert-tls server auth-user-pass verb 3 pull fast-io cipher AES-256-CBC auth SHA512 Config is connected Sun Apr 5 10:50:34 2026 OpenVPN 2.4.7 mipsel-openwrt-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] Sun Apr 5 10:50:34 2026 library versions: OpenSSL 1.1.1f 31 Mar 2020, LZO 2.10 Sun Apr 5 10:50:34 2026 WARNING: --ping should normally be used with --ping-restart or --ping-exit Sun Apr 5 10:50:34 2026 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Sun Apr 5 10:50:34 2026 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Sun Apr 5 10:50:34 2026 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Sun Apr 5 10:50:34 2026 TCP/UDP: Preserving recently used remote address: [AF_INET]217.138.208.91:1194 Sun Apr 5 10:50:34 2026 Socket Buffers: R=[163840->163840] S=[163840->163840] Sun Apr 5 10:50:34 2026 UDP link local: (not bound) Sun Apr 5 10:50:34 2026 UDP link remote: [AF_INET]217.138.208.91:1194 Sun Apr 5 10:50:34 2026 TLS: Initial packet from [AF_INET]217.138.208.91:1194, sid=88021dab 3d3f5cb0 Sun Apr 5 10:50:34 2026 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this Sun Apr 5 10:50:35 2026 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA Sun Apr 5 10:50:35 2026 VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA11 Sun Apr 5 10:50:35 2026 VERIFY KU OK Sun Apr 5 10:50:35 2026 Validating certificate extended key usage Sun Apr 5 10:50:35 2026 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Sun Apr 5 10:50:35 2026 VERIFY EKU OK Sun Apr 5 10:50:35 2026 VERIFY X509NAME OK: CN=us9330.nordvpn.com Sun Apr 5 10:50:35 2026 VERIFY OK: depth=0, CN=us9330.nordvpn.com Sun Apr 5 10:50:35 2026 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 4096 bit RSA Sun Apr 5 10:50:35 2026 [us9330.nordvpn.com] Peer Connection Initiated with [AF_INET]217.138.208.91:1194 Sun Apr 5 10:50:36 2026 SENT CONTROL [us9330.nordvpn.com]: 'PUSH_REQUEST' (status=1) Sun Apr 5 10:50:36 2026 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 103.86.96.100,dhcp-option DNS 103.86.99.100,explicit-exit-notify,comp-lzo no,route-gateway 10.100.0.1,topology subnet,ping 60,ping-restart 180,ifconfig 10.100.0.2 255.255.240.0,peer-id 1,cipher AES-256-GCM' Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: timers and/or timeouts modified Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: explicit notify parm(s) modified Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: compression parms modified Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: --ifconfig/up options modified Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: route options modified Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: route-related options modified Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: peer-id set Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: adjusting link_mtu to 1657 Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: data channel crypto options modified Sun Apr 5 10:50:36 2026 Data Channel: using negotiated cipher 'AES-256-GCM' Sun Apr 5 10:50:36 2026 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key Sun Apr 5 10:50:36 2026 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key Sun Apr 5 10:50:36 2026 TUN/TAP device tun0 opened Sun Apr 5 10:50:36 2026 TUN/TAP TX queue length set to 100 Sun Apr 5 10:50:36 2026 /sbin/ifconfig tun0 10.100.0.2 netmask 255.255.240.0 mtu 1500 broadcast 10.100.15.255 Sun Apr 5 10:50:36 2026 /bin/touch /tmp/lua_bnojmG tun0 1500 1585 10.100.0.2 255.255.240.0 init Sun Apr 5 10:50:36 2026 Initialization Sequence Completed

Okay great so now you'll need to adjust Congestion Control manually, set to Always or Auto (but this depends how SmartBOOST has been setup to prioritize what you care about), experiment with the percentages and see what works best to start giving you better results

Peut être que tu n'as pas mis le mode de contrôle sur "Toujours" et désactivé le contournement de test de vitesse ? C'est la seule façon pour obtenir un A+