All Activity

The update worked very well, only a ping optimization problem does not work. Thanks to your team for this excellent router👍🏻

...Mlab is or was used on the R3 internal speed test live Wan to outside your local network... Ping optimizer is an internal "Lan" test by pinging a server like 8.8.8.8/google.com and simulating a dl/ul bandwidth congestion locally, it tries to stabilize the ping response based on the simulation. If the ping to the server fails then the test fails.

I just got my netduma r3 and set it up with 4.0.540 duma os instantly, but i have problems with geo filtering, it doesn’t have the ristricted mode and ping assist and it connects me to a high ping server even when it’s not inside my zone and when I deny(block) this servers it still tries to connect me to the same server again but because I blocked this server it cancels the matchmaking and i this happening in loop the same thing, what should i do, there is a other lower ping servers in the map, and gives me a higher ping than my isp router

R3_2025-02-21T05_36_13.702Z_logs.txtecco cosa scritto quando si disconnette come risolvo?? mettendo un router in cascata??

Hi. I am finally testing Steady Ping for Valorant. I have our gaming PCs set as Console and added to the Gaming Devices in Geo Filter. I am using Steady Ping (Expert, 10ms, the lowest). I have the shape around North America. Geo-Latency is on, ping assist is off, strict mode on, but I don't have filtering enabled on. Not sure if For Valorant, in game, I am able to select servers, so of course I only select the lowest ping server in California, thus only putting me in well, the California server. Ping without Steady Ping or any Geo settings on is usually around 17-22, but with the recent firmware update, it spikes to 25 or 26. Prior beta firmware was much smoother without Steady Ping. Now I am trying Steady Ping. I have it set as Active for our gaming PC as "console". In-game in the Valorant California server, I get these random connections for Oklahoma, or even Copenhagen. From the Valorant interface, there is no Oklahoma server. I can't say for Copenhagen. I noticed last night when the wife and I were in a match together, mine showed Oklahoma while hers showed Copenhagen. We also had those little graphs that showed steady ping helping. It doesn't always show. What alson baffles me is the note for Steady Ping "When your ping falls below your Target Ping, we'll raise it artificially to keep your connection perfectly stable. Try a number slightly above your usual average ping." Based on this note and knowing my ping hovers around 17-22 / 25, I would imagine setting this Target Ping to 25 would well, keep my ping near that in-game. Instead, it looks like it's adding a LOT of ping to my existing ping. In game it goes to like 36 or so. I thought setting my target ping to the "slightly above average ping" would keep it stable, but rather it keeps it at 36. Instead, I set the lowest target ping to 10ms which keeps my ping around 26-27. Am I going crazy or misinterpreting the steadyping note or completely missing a step? Why is it identifying servers that are completely outside of california? Could it be recognizing another server of some sort, like maybe voice chat being routed through some other Valorant server on the back end? When in a California server, and it's measuring against oklahoma or copenhagen, is this affecting my steady ping / connection? I can't imagine it helps my connection if it's looking at copenhagen. What can I do or provide so Valorant servers can properly be identified? I've seen other posts give some server IDs?

Hi. I am finally testing Steady Ping for Valorant. I have our gaming PCs set as Console and added to the Gaming Devices in Geo Filter. I am using Steady Ping (Expert, 10ms, the lowest). I have the shape around North America. Geo-Latency is on, ping assist is off, strict mode on, but I don't have filtering enabled on. Not sure if For Valorant, in game, I am able to select servers, so of course I only select the lowest ping server in California, thus only putting me in well, the California server. Ping without Steady Ping or any Geo settings on is usually around 17-22, but with the recent firmware update, it spikes to 25 or 26. Prior beta firmware was much smoother without Steady Ping. Now I am trying Steady Ping. I have it set as Active for our gaming PC as "console". In-game in the Valorant California server, I get these random connections for Oklahoma, or even Copenhagen. From the Valorant interface, there is no Oklahoma server. I can't say for Copenhagen. I noticed last night when the wife and I were in a match together, mine showed Oklahoma while hers showed Copenhagen. We also had those little graphs that showed steady ping helping. It doesn't always show. What alson baffles me is the note for Steady Ping "When your ping falls below your Target Ping, we'll raise it artificially to keep your connection perfectly stable. Try a number slightly above your usual average ping." Based on this note and knowing my ping hovers around 17-22 / 25, I would imagine setting this Target Ping to 25 would well, keep my ping near that in-game. Instead, it looks like it's adding a LOT of ping to my existing ping. In game it goes to like 36 or so. I thought setting my target ping to the "slightly above average ping" would keep it stable, but rather it keeps it at 36. Instead, I set the lowest target ping to 10ms which keeps my ping around 26-27. Am I going crazy or misinterpreting the steadyping note or completely missing a step? Why is it identifying servers that are completely outside of california? Could it be recognizing another server of some sort, like maybe voice chat being routed through some other Valorant server on the back end? When in a California server, and it's measuring against oklahoma or copenhagen, is this affecting my steady ping / connection? I can't imagine it helps my connection if it's looking at copenhagen. What can I do or provide so Valorant servers can properly be identified? I've seen other posts give some server IDs? ections to oklahoma or even

by that, do you mean checking off these boxes Peer Ping, Auto Ping Host, Kilometres, Strict Mode etc.? Because I've just done that and it's not working

So changing that IP back to .1.1 caused a lost connection with the Ubiquiti Loco to my shop and still produced the dropped internet here at the house

I changed the router IP as instructed and can confirm there are no devices within the .50-100 range, everything assigned is between .2 and .49

I understand that, I was talking about what specifically are you looking for. Considering there is not much info on the QoS page, and I've told you before what settings I have. Congestion Control is set to Never. Download is set to 600Mbps, Upload is set to 30Mbps. Goodput is checked. DumaOS Classified Games is unchecked, it was checked but I then unchecked it. Either way didn't fix anything. I just tried putting the 5ghz wifi on the Guess side and it still didn't speed up the 2.4ghz wifi, it won't go past 100Mbps often the most is around 90Mbps and used to easily get speeds over 300Mbps. I do notice that whenever I made a change and hit Apply, it takes quite a while before the Wifi signal comes back up. I'm really starting to think the router hardware is broken.

Add me please

ok thanks i did that , i can see the old nas now but im still unable to map any drives to it from my pc. it gives this error any ideas what might be causing this

Can i please has access?

I have brought this up with a colleage and will get back to you once I have some more information.

It shouldn't make a difference in theory but we are dealing with an issue that shouldn't be happening in the first place but could you change the LAN IP back to 192.168.1.1 and see if it is better please? Also you do have some devices using IPs within the DHCP range still

It could well be the DHCP lease issue yes, in which case given your unique scenario it wouldn't be very practical to assign reserved IPs to each device I'm guessing. A potential solution could be to enable DHCP on the TPs/take them out of AP mode, assign the TPs reserved IP addresses on the XR outside the DHCP range, then it if it continues disable DHCP on the XR and then see if it continues.

@FuzyEven then, the roundtrip is unreliable, as you’re aware. I did forget that they switched to the new method, etc. In fact, both methods are used; the first is the mlab, and if it fails, then it’s the roundtrip.

Network Setup: I have a small business network with the following setup: Internet Source: Starlink Enterprise Router: NETGEAR Nighthawk Pro Gaming XR1000 Access Points: 4x TP-Link TL-WA855RE (in Access Point mode) had to go with this ones beacuse of budget cuts. Wired Setup: The XR1000 distributes internet via Ethernet cables to each TP-Link AP. Devices: A mix of wired and wireless clients (not exceeding the DHCP pool). Some users are unable to connect to the internet or get an IP address assigned, even though the DHCP server on the XR1000 should have plenty of available IPs. The problem is inconsistent—some devices connect fine, while others fail to obtain an IP. Restarting the affected device sometimes fixes the issue, but not always. Troubleshooting Steps So Far: Confirmed that DHCP is enabled on the XR1000, with a sufficient IP range. Ensured that DHCP is disabled on all TP-Link APs. Restarted the router and APs multiple times. Could this be a DHCP lease issue or something related to Starlink’s handling of NAT or is this a bug caused by the router because i have seen couple of same issues i just wrote about.

Turn off the PS5 Unplug the ethernet cable from the PS5 Turn on the PS5 Plug in the ethernet cable to the PS5 Check if you have the issue

Sure! Please let me know if anything else is needed. e is needed.

@Netduma Fraser what do i need to do? I dont get it

Disable Adblocker on the router and see if that resolves it please, if not disable BI in Settings > Troubleshooting > Advanced, reboot from the interface, wait 4 minutes then see if it happens again please

I have 500/500 speeds. I reset it earlier and still the same issue. Congestion control is set to 70/70 since running ping optimizer just leaves it at 99/99. And i have tried ping optimizer and running my own and still the same issue.

You wouldn't change those settings unless you needed them, so you just plugged the R3 into that box on the wall and got internet right away?

Change the router IP address in LAN > Advanced, save, reboot from the interface then check if it works