Rahb

Welp I tried I guess and I did resync the cloud and now I got the dpi error. Hopefully @Netduma Fraserand the @Netduma Adminteam have some type of fix as now with this dpi class error ad block and the network monitor are no longer performing as they should 😕 
 
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Tuesday, January 07, 2025 20:00:59
[admin login] from source 192.168.1.3, Tuesday, January 07, 2025 20:00:58
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' now bound, Tuesday, January 07, 2025 20:00:57
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Tuesday, January 07, 2025 20:00:57
[DumaOS] recovering state com.netdumasoftware.dpiclass, Tuesday, January 07, 2025 20:00:57
[DumaOS] Cloudsync DPI result 'true','nil', Tuesday, January 07, 2025 20:00:57
[DumaOS] recovering state com.netdumasoftware.dpiclass, Tuesday, January 07, 2025 20:00:55
[DumaOS] recovering state com.netdumasoftware.dpiclass, Tuesday, January 07, 2025 20:00:55
[DumaOS] Downloading files at mirror: http://api.netduma.com/file/cloud_updates/dpi/0000000242/NETDUMA_V1/gpg/cloud-0000000242-,pi-NETDUMA_V1-gpg.cloud Tuesday, January 07, 2025 20:00:51
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' now bound, Tuesday, January 07, 2025 20:00:50
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' now bound, Tuesday, January 07, 2025 20:00:50
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Tuesday, January 07, 2025 20:00:50
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Tuesday, January 07, 2025 20:00:50
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Tuesday, January 07, 2025 20:00:50
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Tuesday, January 07, 2025 20:00:50
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Tuesday, January 07, 2025 20:00:50
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Tuesday, January 07, 2025 20:00:50
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Tuesday, January 07, 2025 20:00:50
[DumaOS] DPI looking for updates..., Tuesday, January 07, 2025 20:00:50
[DumaOS] recovering state com.netdumasoftware.dpiclass, Tuesday, January 07, 2025 20:00:48
[DumaOS] recovering state com.netdumasoftware.dpiclass, Tuesday, January 07, 2025 20:00:48
[admin login] from source 192.168.1.3, Tuesday, January 07, 2025 20:00:41

nothing happens, it's still the same, the problem is not with Adblock
I have already proceeded with this test and the results are the same, I am encountering the error repeatedly here
[DumaOS] process '//usr/bin/dpiclass' died restart:true, Tuesday, December 24, 2024 12:12:05
[here] Ubus object 'com.netdumasoftware.devicemanager' added, attempting to bind pending, Tuesday, December 24, 2024 12:12:05
every time this command is repeated com.netdumasoftware.devicemanager
we encounter process '//usr/bin/dpiclass' died restart:true
log-1735063987768.txt log-1735061954871.txt log-1735060810354.txt log-1735059544372.txt log-1735059146742.txt log-1735055164945.txt

I have two PC's hardwired to the XR500 aswell as a Xbox series X and non of them are showing up as prioritizing traffic in QOS. I have tried just switching on the standard classified games and i have tried adding the device and creating a rule but nothing is been detected. The PC's mainly play Fornite, minecraft and Fifa and the xbox is Call of Duty. Im on the latest firmware (V2.3.2.134-dumaos33-rc14) and tried a factory reset aswell as redownloading the firmware but not having much luck....
I have had it working in the past and a little unsure when it stopped working, can anyone give some pointers as to where i might be going wrong? Thanks

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
 

I noticed they straight up ignore when this issue is brought up. Im glad we all played beta testers for them just to take all the feedback and use it for the r3 routers. The error still happens on netgears last firmware but doesnt repeat over and over it fails to update from the cloud if you try to sync devices

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

I'll add your name to the list!