IITazII

This is one of the most frustrating experiences of a router. It's so flip flop when it's working and when it's not. 
XR500 V2.3.2.134-dumaos33-rc14 here. It's just constant DHCP renewals, consistent drop outs, and a general mess. Even versioning can't be consistent. 
I don't use QoS or AdBlock. As in, it's not configured 
[DumaOS] DHCP lease change., Friday, May 02, 2025 07:12:58 [DumaOS] DHCP new event., Friday, May 02, 2025 07:12:58 [DHCP IP: 192.168.1.5] to MAC address [xx], Friday, May 02, 2025 07:12:58 [DumaOS] DHCP lease change., Friday, May 02, 2025 07:08:47 [DumaOS] DHCP new event., Friday, May 02, 2025 07:08:47 [DHCP IP: 192.168.1.12] to MAC address [xx], Friday, May 02, 2025 07:08:47 ... [DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Friday, May 02, 2025 07:04:29 [DumaOS] process '//usr/bin/dpiclass' died restart:true, Friday, May 02, 2025 07:04:26 [DumaOS] recovering state com.netdumasoftware.dpiclass, Friday, May 02, 2025 07:04:26  
Under QoS, I have Goodput only checked and have congestion control set to Never. Keeping it on reduces my speeds by a significant amount.
Should I just roll back to the official version and call it a month before I pull my hair out and swap routers for good? 
 
Edit: Yes, I've set the DHCP reservation table for my PC and my reserved addresses start at .50. I start from .2 and go up to around 15 before I'm annoyed. Individually doing them all is ridiculous. It's actually sad to think about all the users and customers who have significant connection issues because they just happen to own this router and don't know how to troubleshoot it. I don't think my smart bulb needs a reserved IP. 😛

It is already working, you can update

It is already working, you can update

It is already working, you can update

It is already working, you can update

A BETA a year and a half later? This version is prepared for the public and depends on NETGEAR making it public, QOS cannot fail even if it is BETA, it is a router that is said and promoted as the best QOS on the market, and we end up grateful for fixing it. ..

A BETA a year and a half later? This version is prepared for the public and depends on NETGEAR making it public, QOS cannot fail even if it is BETA, it is a router that is said and promoted as the best QOS on the market, and we end up grateful for fixing it. ..

A BETA a year and a half later? This version is prepared for the public and depends on NETGEAR making it public, QOS cannot fail even if it is BETA, it is a router that is said and promoted as the best QOS on the market, and we end up grateful for fixing it. ..

You are probably reading this too late. For those that are reading this first -  STOP - this beta version does NOT work. Fraser, you’ve wasted a lot of people’s time by STILL not giving people a precaution. If you have been unfortunate to install this beta version, go to Page 18/19 & read what I did/had to do. Short version is I reinstalled the old firmware & over a month later it’s been working flawlessly. Not had a single issue, QOS has been working perfectly fine too. 

hi I have had loads of trouble with this router in  from the updates   wish that they would step up and give us a fixed  software for this  I have spent hours trying  to get  it to load after a simple reset on  the beta rc 14 and 10  but managed to get into the index and flash it again to get into it once again   please give us  the  fix we all deserve    for the xr500   loads of unhappy people on here  waiting   

I already did the tftp thing, the problem appears after a few minutes, I think it is when it synchronizes with the cloud, because when I deactivate QOS the error disappears, I think it is a "DPI" application that blocks the others or it does not synchronize well with the cloud

This is sad that we bought these router and was taunted these great beta features only to have them give up on us so they can focus on their own platform the R3. It’s almost like we’re just the community of test dummy’s. Just give us a working firmware with these features and we will all be happy. 

We pushed out a cloud update this week that's being applied incrementally, by tomorrow it will reach 100% rollout. You can also resync the cloud to get it. If that doesn't fix it please downgrade - though it is more likely to be cloud vs firmware given the recent nature of the issue.

NO, the same thing happens to me and the solution is not mentioned or why it happens, when this "error" started to appear QOS and ADBLOCK do not work

The  🐘 in the room 
-  by L2W
Dear Fraser, since you do not want to respond/answer, i think some else could from the Netduma Team could shed some light on this?
I hope this message finds you well.
I’d like to express my frustration with the situation surrounding the XR series routers (Specifically the XR500 and XR1000), as it feels like we, as customers, have been left behind while new products and updates are being prioritized for the R-series.
When I purchased the XR500 and XR1000, I did so believing the promise of a cutting-edge, future-proof gaming experience powered by DumaOS. At the time, I invested nearly $500 into the two routers, fully expecting that the firmware updates would continue to enhance their functionality and gaming features. However, the reality has been far from that expectation. Despite being marketed as premium gaming routers, the updates have been inconsistent, delayed, and in some cases, non-existent.
Now, with the introduction of the R3, it feels as though customers like myself who purchased the XR series are being left behind. I understand the need for new products, but I cannot help but feel that the focus on the R3 has effectively sidelined the XR series, especially with the news that DumaOS 4.0 will not be available for the XR series. This is incredibly disheartening, as it appears that users who invested in the XR routers are now facing outdated firmware, while the R-series is receiving the latest features.
I believe this situation could have been handled differently, particularly given that Netgear is not a small company. If Netgear is truly committed to its customers, particularly those who have invested in the XR series, it should not deny them access to the latest firmware updates that bring the promised gaming features. Denying these updates is not only poor customer service, but it also undermines the trust that customers have placed in the brand.
If the focus is indeed shifting entirely to the R-series, it would be much more transparent to acknowledge this and provide clear communication to customers regarding the future of the XR series. It’s frustrating to feel like I’ve been caught in a cycle of purchasing products that, at the end of the day, are rendered obsolete faster than I could have ever anticipated.
As it stands, I’m left wondering when—or if—there will be any updates for the XR series to bring them up to the same level of functionality as the R3. The lack of clarity and consistent communication about this issue is disappointing.
I’d also like to raise the point that Netgear’s partnership with DumaOS should be focused on providing a top-tier experience for all users, regardless of which series router they own. Denying updates or withholding features for older products feels like a missed opportunity for both Netgear and DumaOS to show their commitment to their customer base.
Thank you for your time and attention to this matter.
Best regards,
L2W

I do not mind being the 🐘 in the room. SOMEONE HAS TO . 
LETS TALK ABOUT IT !





@Netduma Admin
@Netduma Adrian
@Netduma Alex
@Netduma Anas
@Netduma Andy
@Netduma Bruno
@Netduma Cameron
@Netduma Casey
@Netduma Crossy
@Netduma Eyitope
@Netduma Fraser
@Netduma Greg
@Netduma Iain
@Netduma Jack
@Netduma Jack B
@Netduma Jonathan
@Netduma Joseph
@Netduma Josh
@Netduma Justas
@Netduma Kacper
@Netduma Kieran
@Netduma Lew
@Netduma Liam
@Netduma Luke
@Netduma Luke M
@Netduma Manu
@Netduma Nicola
@Netduma Sam
@Netduma Samuel
@NETDUMA Santa
@Netduma Tom
@Netgear Router Setup
@DumaOS Beta Testing
@Nighthawk Pro Gaming

HAPPY FRIDAY! . 🥳🤩
Now that's about as nice as it gets. 

"JUMPS IN THE SHALLOW END [HEAD FIRST]" 👀


Alright, @Netduma Fraser -🤬
Brace Yourself , This is not directed towards you personally, i mean you personally took this job , so give me as personal as it get's with DumaOS? 
I spent nearly **$500** on 2 XR routers (XR500/XR1000) because I believed the hype: “The ultimate gaming router powered by DumaOS.” But instead of cutting-edge features, I got stuck in a never-ending cycle of broken promises and half-delivered updates. Now I’m hearing that to get the latest and greatest features, I have to drop another **$200** on the R3? So, I’m out almost **$700** just to stay current? Seriously, why did I even buy into the XR series if the “future-proof” promise only applies to someone else’s hardware? Oh wait ... That's your own hardware (SOLD SEPERATELY) 
And let’s not ignore the elephant in the room: **DumaOS 4.0.** The fact that it’s “never coming to the XR series” 🤯says everything I need to know. Why invest in a product that’s been abandoned before it’s even reached its potential? Meanwhile, R-series users are enjoying the full experience, and XR users are left to rot on outdated firmware, i mean "Based on IOU's" and "We don't have a beta or know when it will be available" IN any other company - SAME SCENERIO. [Hey bruce, "rolls chair around with a quick swivel then pivot" , What's up Chad? Where we at on the beta for the LOL10000PEW's Firmware? Oh One second Bruce, "rolls chair around witha quick swivel then pviot" keys clacking on keyboard. Whips its backaround. So Bruce, were looking like 2 weeks tops. Thanks CHAD! . Oh one can dream .... I mean NETGEAR doesnt have to APPROVE the Beta Versions. Just DUMAOS right> . By the time we get DumaOS 3.3, the R-series will probably be running on version 6.0, complete with features we were promised from the start. (A Box can be so misleading)  
It’s painfully clear this was the plan all along:  🤡
1. **Market the XR series** as cutting-edge gaming routers.  
2. Promise firmware updates that never arrive.  
3. Launch the R3 and make it the real star of the show, while XR users are told to sit tight.  
4. Leave XR users permanently one step behind.  
Let’s face it, this is a **brilliant marketing scheme**:  🥸
- Netgear pulls in customers with promises of premium gaming features powered by DumaOS.  
- Updates for XR routers get delayed indefinitely.  
- DumaOS shifts focus to their R-series, forcing loyal XR users to spend more money just to stay relevant.  
What’s next?🤑
The **XR2000** in 2030?
The **XR-StillOn3.3** in 2035?
By 2040, we’ll get the **XR-HopeYouDidn’tWant4.0** with a tagline that reads, “Firmware coming soon… we promise.”  
At this rate, we’ll have routers named after the stages of grief:  🙄
- XR1000: **Denial** – “They’ll release the update any day now!”  
- XR2000: **Anger** – “Why am I still waiting for this update?!”  
- XR3000: **Bargaining** – “Maybe if I tag Netduma everywhere, they’ll care.”  
- XR4000: **Depression** – “Still stuck on 3.3, but I’m too tired to care anymore.”  
- XR5000: **Acceptance** – “Guess I’ll just buy an R3 and move on with my life.”  
And the best part? This isn’t just disappointing—it’s insulting. It feels like we were used to build a customer base for DumaOS, only to be abandoned the second they decided to roll out their own hardware. “Thanks for your money; here’s an outdated firmware to remember us by!” 😭 
Honestly, it’s like buying a sports car only to find out it’s missing the engine. “Oh, you wanted speed? That’s in the R3 model. Would you like to upgrade?” At this point, the only thing “cutting-edge” about the XR series is how it cuts into my wallet.  🤣
So, Fraser, where does this leave us?👀 Because from where I’m standing, XR users are nothing more than an afterthought in Dumas's bigger plan.
Convert the customers of XR Series (NETGEAR) to R Series (YOUR COMPANY's ROUTER)
Slowly pick off the customers of NETGEAR and take them all for yourself. Brilliant!

Final Note - Since R3 is already out and kind of "meh" as is been quite some time that the "hype" of the R3 is kind of no more. (No disrespect, just in regards to a WIFI 6 Gaming Router to Others out their)
When should i expect to purchase the R4-Wifi 7 - A router that can compete with todays Gaming Routers ( i wont list your competition, but GOOGLE will!) 
- Spoiler Alert - Check the "specs sheet" between an R3 vs XR1000
It all lies in the software.... ultimately DumaOS

Seriously - Wallet in Hand. I'm ready to buy today

P/S - Don't get to this point and be salty😅. This is easily my way of letting my opinion get the best of me. Notice i didn't mention you (except Frazier) , so don't take anything i said personal. That goes for all (including Frazier) - " This was meant in no way shape or form to single any(one-person) out OR in no way to be disrespectful" Its a forum, for this exact reason. 😶

LETS TALK ABOUT IT! 

Thank you for your time ,
L2W
 

This has been said and so far they do not offer a solution.
go back to the official Netgear version, there is no alternative

Same error and no solution

[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:20:19
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:20:17
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:20:15
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:20:13
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:20:11
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:20:09
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:20:07
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:20:05
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:20:03
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:20:00
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:58
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:56
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:54
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:52
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:50
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:48
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:46
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:44
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:42
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:40
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:37
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:35
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:33
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:31
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:29
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:27
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:25
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:23
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:21
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:19
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:17
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:14
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:12
[admin login] from source 10.0.0.2, Thursday, December 05, 2024 07:19:12
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:10
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:08
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:06
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:04
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:02
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:19:00
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:58
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:56
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:54
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:52
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:50
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:48
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:46
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:44
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:42
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:40
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:38
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:36
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:33
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:31
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:29
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:27
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:25
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:23
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:21
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:19
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:17
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:15
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:13
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:11
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:09
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:07
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:05
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:03
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:18:01
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:59
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:57
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:55
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:53
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:50
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:48
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:46
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:44
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:42
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:40
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:38
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:36
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:34
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:32
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:30
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:28
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:26
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:24
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:22
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:20
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:18
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:16
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:14
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday, December 05, 2024 07:17:12
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Thursday,
 
once this error happens which takes about 3-4 hours after a factory reset causes network monitor to stop working everything is unknown  which causes qos to stop working and traffic prioritization no longer works. no games detected nothing. ive tried 10 13 and 14 beta version and the firmware before beta it still happens which tells me this is on yalls end. get it fixed

Apparently all routers that use duamos have faulty firmware.

Creo que deberíamos crear una plataforma de afectados y denunciar a Netgear y a todos los implicados en el desarrollo del enrutador, esto ya es una estafa a gran escala y no se puede permitir. Llevan mucho tiempo tomándonos el pelo con una actualización que no llega, y los responsables de DumaOS, solo saben decir que no proporcionan beta y le echan la culpa a Netgear. Son unos auténticos vende humo ya que lo mas responsable es crear una actualización del sistema DumaOS para un enrutador que es sin duda el mas caro de la gama XR, habiendo ya actualizado todas las versiones y dejando tirados a los que compramos el tope de gama, el XR1000. No me vale que digáis que depende de Netgear cuando el sistema es de DumaOS, lo que os obliga a cumplir con el cliente creando una beta y enviándola a todo usuario que la solicite sin contar con Netgear. Netgear a fabricado el producto, y para que el producto funcione depende de vuestro sistema, por lo que ya es algo entre DamaOS y sus usuarios, aquí no pinta nada Netgear.

liteally same, dumaos is screwing joke right now. he is consitently blaming Netgear but we all know what is the problem. 
I bought cheaper asus router and it works much better lmao 

Duma os is faulty period

Frasier you're cool man. I guess you have to reply to us with something because that's what your genius company outlined you to do.... But if you report to anyone just show them this. I donno. I come from custom firmware router world before this xr1000.  I'm not an average user. No matter what issues we report to you all you're going to end up in the end saying is to reset the router. When it's all said and done after we've told you every single issue and nothing works. You're going to say to reset it and it still won't work because I and I'm sure everyone else have tried this.... We just need you to either explain to management the need for firmware updates or perhaps let us know another way since you won't be able to speak candidly here that it will never ever happen and we should move on from Duma os and Netgear. Because I sure have false hope that a firmer update will release magically either updating this to an entirely new operating system version all together or finally fixing something. " This Rapp is taking longer to load than expected " can be reproduced on any Windows, operating system or web browser by simply just hitting apply every second or third time. That is the error message... You're going to tell me to use another browser or another operating system or another computer reset my network settings. Make sure I have no ridiculous firewall settings... You might suggest to reinstall Windows if you're crazy lol and don't read or a bot... I don't think you're a bot  Fraser... We really just need some support in the firmware area. Perhaps AI can fix some bugs?. Seems to work for Nvidia lately. Seems to work for Nvidia lately. Or perhaps gather some managers and another thread and we'll all talk and have a nice discussion as to why a company releases a product that isn't quite ready for release.... But then we're going to have to bring the entire AAA gaming industry into that lol. 
This is just comedy for any frustrated user of reading this at this point Frazier, but for real, tell these people to get some more updates going or figure out how to give us Duma OS. Whatever version you're up to. I'm sure it is a memory issue perhaps here's an idea....
 
Of Nvidia again for instance will release different firmwares for their graphics cards. One for overclocking one for not... Perhaps you guys can have a Duma OS light version?... Something with less features that just works that we choose to put on that doesn't come factory? 
That should require less coding. Probably a new build but everything takes 3 years with you guys anyway so.. don't steal my ideas Frazier 
You tell them senorlasopa said so!
And if I offended you Frasier in any way just look for my YouTube channel...it will all make sense.

They just want people to buy the R3 rather then fix the issues its not hard to see that support is poor from both sides netgear & Duma just blame each other if they want a happy customer base they need to step up and admit and look on how to resolve things instead we are told to wait no ETA and its down to netgear seems like they dont communicate with each other very well..