All Activity

I pre ordered an R2 a long time ago directly from the Netduma site and never used it, it sat unused in my cupboard for many years (I got new fibre internet during the pre-order wait and then never got around to using the R2) Recently I finally took it out of the box to try out. I'm unable to access the user interface though. I've tried holding the reset button for 50 seconds whilst plugged in, then 50 seconds whilst it's unplugged, waited 5 minutes and plugged it back in + ran an ethernet cable from the LAN 1 port of the R2 to the LAN port on my PC - I still cannot access the user interface. I've tried changing my network adapter to use: IP address: 192.168.77.10 Subnet mask: 255.255.255.0 Default gateway: 192.168.77.1 That also doesn't work. I've tried a different cable & port, still nothing. Running ipconfig doesn't even show a default gateway. What else can I try? Thanks in advance for any help. Kind regards, Joe

Thanks for the explanations. I can't connect to the 5 GHz and I don't know why. It happens just with netduma. I can connect my computer to every 5Ghz wifi.

Salut ! C’est un routeur de jeux ! 😉 En automatique, il prendra en compte le signal proposé avec la meilleure latence pour jouer ! Tu dois séparer les bandes et les régler manuellement si le but est d’obtenir les meilleurs débits !

I see. Maybe my test was glitching out I’ll try the ping. my line as previously mentioned is 900 down and 115 up. Duma OS router speed test sometimes will give me 888 or 907. Upload is 107-105. So I gone in and manually added 900 and 115 Hopefully this will help lock in results. I know 80 percent is a good value for download so I’ll do some more bb testing and focus on upload turning.

Report: 5GHz channel width limited to 20MHz with MediaTek MT7921 Wi-Fi 6 client — Netduma R3 Summary With a specific WiFi 6 client (MediaTek MT7921 chipset), the Netduma R3 never negotiates a channel width wider than 20MHz on 5GHz, regardless of the channel/bandwidth settings configured on the router. The same client, under identical signal quality, correctly negotiates full bandwidth (80MHz, 1201 Mbps link rate) with a different 5GHz access point in the same environment. Other client devices (e.g. a smartphone) reach normal speeds on the same Netduma R3, so this is not a general issue affecting all clients. Devices involved Router: Netduma R3, firmware v4.0.1147 (latest version available at time of testing) Affected client: HP Victus by HP Gaming Laptop 16-r0xxx, MediaTek MT7921 Wi-Fi 6 802.11ax PCIe Adapter Client driver: MediaTek Wireless LAN Driver v3.5.0.89 Rev.E (latest official HP release, freshly reinstalled during diagnosis) Key data point: direct comparison at matched signal quality Measured at the same time, same physical laptop position, via netsh wlan show interfaces: Network Channel Resulting bandwidth Signal RSSI Negotiated rate ISP router (TIM, different 5GHz AP) 64 80MHz 78% -62 dBm 1201 Mbps Netduma R3 36 20MHz 78% -63 dBm 286.8 Mbps Signal and RSSI are essentially identical between the two networks (1 dB difference, negligible). The rate negotiated with the Netduma R3 is still a quarter of what's achieved with the other router, consistent with a drop from 80MHz to 20MHz channel width (2 spatial streams, MCS11 in both cases — only the channel width differs). A second device (smartphone) connected to the same Netduma R3 on the same 5GHz band reaches real-world throughput up to ~600 Mbps, so the Netduma R3 is not globally stuck at 20MHz for all clients — only for this specific MediaTek MT7921 chipset. Measured impact on real throughput WiFi on Netduma R3: real throughput varying between ~130 and ~290 Mbps download depending on the test, with upload bufferbloat often elevated under load (300-450+ ms in several tests) Ethernet cable on the same Netduma R3: 688 Mbps download / 952 Mbps upload, bufferbloat +27ms download / +31ms upload (excellent) — confirming the bottleneck is specific to the WiFi radio, not the rest of the router/QoS engine Causes ruled out during diagnosis Before isolating the issue described above, the following causes were tested and systematically ruled out, both router-side and client-side: SmartBOOST: Gaming/Video & Streaming/VPN activity priorities lowered to minimum (1/1000) — no change in the declared bandwidth reservation or in real throughput 5GHz channel/bandwidth on the router: tested both on automatic and manually forced (channel 36, 80MHz) — no stable improvement Client protocol (802.11ax vs forced 802.11ac): forcing 802.11ac made the negotiated rate worse, not better Windows regional/regulatory domain: verified correct (Italy) WiFi adapter power saving: already set to "Maximum Performance" on AC power Bluetooth (antenna coexistence on the combo chip): fully disabled, no change Congestion from neighboring WiFi networks: zero third-party networks visible in the scan RSC (Receive Segment Coalescing): found globally disabled on Windows; re-enabling it made results noticeably worse Windows QoS policies (Get-NetQosPolicy) and Group Policy bandwidth reservation: no policy present Windows NetworkThrottlingIndex: modified/fully disabled, no effect Packet loss: 0% over 50 consecutive pings to the router, 1-4ms RTT — base connection stable CPU/driver load: no process or core saturated during speed tests Network driver: full clean reinstall (uninstall + latest official driver from support.hp.com) — no change Laptop BIOS reset to factory defaults: this did meaningfully improve the laptop's general WiFi performance (confirmed by the jump to 1201 Mbps with the other router), but did not resolve the specific limitation with the Netduma R3 Connection caching: Netduma R3 restart and "forget and reconnect" of the WiFi profile on Windows — no change in either case Request We would like to know whether this is a known interoperability issue between the Netduma R3's 5GHz radio and MediaTek MT7921 (WiFi 6) chipsets, and whether a firmware fix is planned. We're happy to provide further logs or repeat specific tests on request.

Is it possible to add Gundam Battle Operation 2 for PS4, PS5 and PC to the Ping Heatmap?

Sorry to hear that but at least you've got a working solution and you could take your anger out and make it look better!

I've given you Early Access so you can upgrade to that version to see if it helps: https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/ If not please provide a log from the router when the issue next happens Great keep us posted!

I wouldn't have thought it would affect download as well so it may be more to do with how the test is performed. You could perform a big upload and do a ping test alongside and change the percentages to see if it is actually affecting it like the test says.

I've added you both to Early Access where you can see the massive change log for the firmware also: https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/ It's primarily a bug fix/stability update so I think it's quite stable based on feedback so I'd suggest upgrading to it. I haven't seen that issue so it would be good if you could upgrade and then let us know if that continues.

It would be a necessary server, usually if you're in the EU you would see one in the EU although it can from time to time be located in the US. It's possible it's mislocated also, if you ping it you could tell.

it doesn't work for everyone, we are waiting for NTGR to provide a solution

Thank you for the access to the latest firmware. I will install it and make some tests. I didn't change anything regarding settings, until I started to play with the R3 versions. The ISP modem brand is a Skyworth GN543V. It looks like my ISP can't set that modem as bridge, so they offered me a DMZ so that's what I'm using. I will also be testing out the issue with others routers that I owned in the past, so I can have more options to determine better if it's an issue by my ISP or the R3 itself. Thank you guys

I am having a similar problem. My wife has been complaining to me for the past couple of weeks about the internet going out for a few seconds while she is working on her computer and zoom/teams calls dropping. I have tried restarting both the router and my modem with no success. I have not changed any settings or my set-up. Any ideas on a fix?Thank you

I’ve done that a few times as well. The U.k,Paris, South America ping was around 110. I don’t even add steady ping but I’ll try it

So today I tried setting the VLAN ID to 0 with the bridge device plugged in. It didn’t have any effect and there was no successful connection (red internet light). However, even with the Enable VLAN / Bridge Setup set as inactive in Advanced Settings, the router doesn’t get a successful internet connection from the bridge device at all now. Before it would at least get a successful connection despite the connection drops (which I am still witnessing on the bridge device). I have a feeling my ISP may have done something on their end after my last phone call, but I’m truly past caring now and can’t be bothered to speak to them again. I’ve begrudgingly attached the Dasan to the wall, but I did rip off the antennae which was mildly satisfying. @Netduma Fraser & @DARKNESS - thanks again for your replies.

Thanks for response. So I did that. I found 75 added no bloat, going up to 80 then offer same result. So 85 and up seems to be bloat city. So for download I stuck on 80. If I had 85 down and 95 up my download values and jitter was below 1ms. If it lower my upload lower, my download ping values increase and jitter could hit 6-15ms. So it seems strongly shaped can add more impact to download. Do you think this is just noise or can capping upload on fttp cause issues?

A versão 4.0.540 é a melhor ainda jovem! Testei a versão beta por meses e cheguei a conclusão que a versão pública 540 é a melhor para jogos, principalmente no controle de congestionamento.

Are there any major changes in the beta from .540? Would I be better off staying on .540 until the official release of the updated firmware? I also performed a factory reset recently due to a power outage during a reboot and the Wi-Fi LED's turned off, is that a bug and will it be fixed in the beta firmware? Sorry for all of the questions. I request to be added to the beta, please. Might as well pull the pin on that and see what happens. Thank you for all of your hard work and have a great day.

That actually makes sense. Yesterday, I played a few matches with 90ms latency. I have a question: when I start my PS5, there's an initial connection to a dedicated US server, which I assume is the PSN server. Is it normal for this initial connection to be in the US and not Europe? Since it's a dedicated server and I don't have its IP address, I can't block it to see how it behaves in games.

Hello, can I have access to the current latest beta firmware?

Pretty certain that's the cloud issue causing you to be unable to match with French/EU servers, however it's impossible for you to get 35ms ping to the US server so for whatever reason there is a mislocated server there that you can connect to so that one will be elsewhere in Europe, it's not actually a US server. Move it around and see if you can find a proper US server - you should be seeing at least 70ms to one.

Yeah that bufferbloat test or using PingPlotter with those reductions in percentage is a good way to fine tune it. Don't use the in built test, depending on the available servers/where they are in relation to you they can provide abnormal results.

It looks like unloaded your jitter is around 3ms so you're not going to be able to get it better than that as that's the inherent stability of your connection. So I don't really think there is much if any room for improvement there. I would suggest forcing some servers further away, although you'll get a slightly higher ping the server load may be less allowing for a more even experience.

If you go out of the US, keep SteadyPing as low as it can go. For me, the UK and Australia are my lowest pings around 140ms I’m in Arizona. Texas I’m at 27, and the east coast I’m in the 50’s and 60’s.