All Activity

mas foi apos essa nova atualizaçao que ficou assim os valores nao estao corretos com o contratado, antes dessa atualização estava tudo certo pode ser erro do software ?

Salut ! Le test de vitesse est une science imparfaite ! Il se base sur un serveur spécifique qui ne peut pas atteindre vos vitesses FAI ! Le plus simple est de mettre vos vitesses max FAI Ethernet 940/500 Mbps manuellement !

bom dia após atualização para 4.0.1510 o r3 não aparece a velocidade da banda larga hoje tenho 1G dow / 500mg up e quando faz teste no r3 chega 200/140 quando testado direto no modem a velocidade fica ok mas quando testa no r3 diminuiu muito foi após essa última atualização que ficou assim pode me ajudar obrigado

Good to hear, thanks for the update!

It's not a necessity but you can if you would like to

Dear Netduma Support Team, I am writing to express my frustration regarding the continued lack of proper Geo-Filter support for EA SPORTS FC 27 on the Netduma R3. FC 27 has already been released for several weeks, yet the game has still not been officially added to Geo-Filter. We experienced the same issue with FC 26, which was never properly added either. There are several problems that need urgent attention: 1. FC 27 is still missing from Geo-Filter Despite being a major online competitive game, FC 27 is not officially supported. Netduma should be keeping its game detection and server database updated, particularly for popular annual releases like EA SPORTS FC. 2. Istanbul servers are incorrectly identified as Frankfurt When connecting to the Istanbul server, Geo-Filter incorrectly displays its location as Frankfurt, Germany. This makes accurate server identification and geographical filtering unreliable. 3. Server ping functionality is not working Geo-Filter is unable to ping the detected game server correctly, preventing me from monitoring its latency and connection quality. 4. Steady Ping cannot be applied Steady Ping does not activate or function correctly with FC 27. This is one of the main features advertised for improving connection consistency, yet it is unavailable for the game I primarily play. 5. The same problems have continued across two game releases FC 26 was never properly supported, and now FC 27 is experiencing the same situation. This raises serious concerns about the frequency of game compatibility updates and the long-term support of the Netduma R3. I first reported the Istanbul server detection issue on July 17, and I was told it was being investigated. Despite subsequent firmware updates, the problem remains unresolved. I would like clear answers to the following questions: When will FC 27 be officially added to Geo-Filter? When will the Istanbul server be correctly identified and positioned? When will server ping functionality work properly? When will Steady Ping become fully compatible with FC 27? Is Netduma actively updating its EA SPORTS FC server database, or are users expected to continue playing without these features? I purchased the Netduma R3 specifically for its gaming-focused features, including Geo-Filter and Steady Ping. These features are major selling points of the product, and customers should reasonably expect them to work with current mainstream competitive games. We should not have to wait months after every annual EA SPORTS FC release for basic compatibility. I am not looking for generic troubleshooting suggestions such as restarting the router, changing DNS settings, or resetting Geo-Filter. I am requesting an actual compatibility update and a clear response from the development team. Please escalate this issue to the DumaOS development team and provide a concrete update on the status of FC 27 support. Thank you. Best regards, Netduma R3 User

Thanks! Do i need to factory reset after the firmware update like we did before?

Hi Fraser, Thanks for the advice! I always keep my Wi-Fi bands separated and stick to 5GHz for the PS5 Pro since the ping is way more stable for gaming. I reinstalled v4.0.1510 today and did a factory reset, then put both bands to the test while playing Battlefield 6 with two devices streaming video and a third downloading a torrent: - 2.4GHz: DumaOS showed 'Excellent' signal and the PS5 hit 94-96%, but the ping spiked all the way up to 160ms and I couldn't get it to stabilize. I even dialed Congestion Control down to 10%, but it didn't help under that load. - 5GHz: Signal status in DumaOS fluctuates between 'Very Good' and 'Excellent' (PS5 shows 100%), but with Congestion Control at 60%, gameplay was rock-solid—zero ping spikes and zero packet loss under the exact same load. I originally suspected a Wi-Fi issue because on v4.0.1147 the signal reading was consistently 'Excellent' across all devices. On v4.0.1510, the signal reading started fluctuating, and I had ping spikes alongside those drops previously. Right now, despite the visual signal fluctuation in the UI, gameplay feels completely smooth on 5GHz. I'll keep monitoring performance over the next few days and let you know if anything changes. Cheers!

I've not heard anything but I will chase the team, thanks for the reminder!

Have you specifically split the WiFi bands and connected to the 5GHz? Overall 2.4GHz is better for stability, do you have a better experience with that on the latest version?

Hi Netduma Team, I would like to report a Wi-Fi performance/stability regression introduced in firmware version v4.0.1510 on the Netduma R3. Setup details: - Router: Netduma R3 - ISP Modem/Gateway: FRITZ!Box 7530 - Primary Client: PlayStation 5 Pro (connected via 5 GHz Wi-Fi) - Placement: R3 is on the ground floor, PS5 Pro is on the first floor almost directly above it. Issue experienced on v4.0.1510: - After updating to v4.0.1510, the Wi-Fi signal quality degraded noticeably in DumaOS, and frequent in-game "unstable connection" icons and ping spikes occurred on the PS5 Pro. - Troubleshooting steps taken on v4.0.1510: Performed a full Factory Reset, deleted and re-added the Wi-Fi network on PS5 Pro, adjusted antenna angles, tested fixed channels (36–48) and forced 20 MHz / 40 MHz channel widths. None of these resolved the ping spikes or signal instability. Workaround / Resolution: - I downgraded the R3 back to firmware v4.0.1147. - Immediately after the downgrade, Wi-Fi signal quality and connection stability fully restored. The PS5 Pro shows 100% signal strength, and all in-game ping spikes and instability warnings completely disappeared. This suggests there may be a Wi-Fi driver or RF power management regression in v4.0.1510 affecting 5 GHz penetration through floors/walls. Hope this data helps with the next firmware build!

hello any news about adding the game into the cloud? @Netduma Fraser

All the firmware versions can be found here: https://www.netgear.com/support/product/xr1000 the only differences between the versions though are security fixes basically. I'd guess that you need to enter your expected/paid for speeds now and then it will work fine. You can do so in the Congestion Control menu

Great to hear that, thanks for the feedback!

It doesn't really matter the bufferbloat result you get in this setup because any of the devices connected to the TP could cause you to lag on the R3 so I wouldn't stress over the value too much

Hi Mercy, to roll back to firmware version 1.0.0.74, tap on Knowledgebase in the Duma Forum. From there, look for Firmwares, then select XR1000. It’s pretty straightforward from there.

Is there a link i can download the firmware version 1.0.0.74 to rollback to? The 1.0.3.88_2.1.43 firmware version doesn't seem to work very optimally. When i installed it i got a screen basically asking if i wanted to run a test to help improve internet speed or ping or something to that nature. I ran the test (which didn't improve my speeds or ping at all) and now get half of my internet download speed even though QoS is set to never in the interface. Plus connection benchmark don't work anymore based off other experiences including mine.

merci 🙏🏼 la mise à jour à apporter les corrections qui faisaient défaut. J’ai testé tous les paramètres du menu et tout fonctionne correctement. j’avais des problèmes sur l’optimisation du ping même ça cela fonctionne parfaitement. Enfin merci à la team.🥂

esattamente, vorrei sfruttare i 2,5 della mia connessione per tutto il resto della casa. ad ogni modo a questo punto, potrei eliminare il router dell'isp e passare direttamente ad una connessione ppoe. C'è solo un problema, per avere un buon risultato nel test del bufferbloat, devo castrare moltissimo la mia rete, arrivando a valori del 20/30% del valore della banda totale.....

@dmessn22 I can't see how an update would specifically stop a matchmaking playlist from working but I suspect if you upgrade again it would work fine

Understandably you want devices to have access to the other 1.5Gbps you pay for but it does mean that the R3 isn't controlling your entire network which means getting a good result on the bufferbloat test is very difficult. From a purely best connection standpoint for gaming you should have the TP-Link connected to the R3 instead so it can control your network but it would mean losing access to that extra speed.

Ciao a tutti, leggendo in giro sul forum, mi stavo chiedendo se la mia configurazione della rete di casa, sia corretta: ho una connessione fibra da 2,5/1, gioco da ps5, ma le prestazioni, non sempre sono costanti. ho il router dell'isp collegato all'ont (con wifi disabilitato) netduma r3 collegato in cascata e in dmz sulla porta da 1 gb che ha collegato solo pc e ps5 (anche r3 con wifi disabilitato) un router tplink in modalità acces point, che fornisce il wifi a tutta la casa, collegato sull'unica porta da 2,5 del router dell'isp. l'r3 ha valori molto castrati per otterenere questo bufferbloat. C'è qualcosa di sbagliato o che posso migliorare?? Grazie a tutti

That's great to hear, thanks for the update and you're very welcome!

This is my personal view but I don’t think they branched out, still using cache on the web browser, it’s really old tech. The Internet has moved on and so is networking And that’s why companies like UniFi who are not that old, 2005 if mem serves me well but look how they have grown. I can see company house reports because in the UK companies have to publicly show reports. They could’ve easily produce a gaming router, normal routers and grown and developed into more hardware and different market segments. My personal point of view and the again is my personal point of view the hardware is lacking and it’s outdated software. If I look in the Philippines the majority game on mobile phones. The majority use a generic router. A Niche market is risky, I just wish they had branched out more in the early days. and here’s the thing you can walk into an airport go onto the public Wi-Fi and make perfectly stable video calls, and that’s with thousands of people using that network. networking has moved on a great deal, I just wish they had moved on with it. I believe they could’ve had a decent company covering different aspects of networking. That’s my personal point of you and it would’ve been great to see a British company competing against other companies. I’m still in the U.K. at the moment, flipping between countries and I talk to better half with no latency issues and she sat in a very basic provincial house using a generic router. It’s not even set up in a good place it’s in the corner of the house and next to it is the solar system which I put in.

Just something from my experience: Wanted to flag this in case it helps anyone in the future. I’m on an R3. I was on DumaOS 4.0.1510, app 4.0.290. On October 2, around 11:10–11:30 PM EDT, Black Ops 7 matchmaking broke. Ranked and multiplayer had both been fine earlier that night. Ranked died right away. Lobby Not Found, error cause 10, error code 2029. Multiplayer was slow to find a game at first, then worked again around 25 ms ping (usually I'm around 7-11 ms). Ranked never came back. I was queuing alone on Battle.net, wired into the R3, on fiber, with NAT Open. Account is not banned. Geo-Filter was off, and I hadn’t changed any in-game settings. I tried the usual stuff. Scan and repair, flush DNS, renew the adapter, power-cycle the ONT and the R3, terminate/repair/reset the game, and a full uninstall and reinstall. I also launched the same game through the Xbox app instead of Battle.net, and I joined a friend’s party. Ranked still failed every time. Plugging the PC straight into the fiber ONT and skipping the R3 let Ranked queue normally, so I assumed it was the router. Downgrading to 4.0.540 by itself did not fix it. A factory reset after that did. Ranked has been fine since. Not sure if the reset cleared something left over from 4.0.1510, or if the reset itself was what fixed it. Happy to share the Activision support notes if you want them. Not much in them other than the Support agent telling me to do some basic troubleshooting.