Netduma Liam

That's odd, so you reset, re-added the rules and they were fine for a month or so, then they stopped working? Is that correct? Did anything change or did you make and other configurations around the time you noticed the issue occur again?

Welcome to the forum. It's in Traffic Prioritisation and will be automatically prioritised by the DumaOS classified games rule when detected. I don't recall whether or not we can add it to Geo-filter/Ping Heatmap, let me check with the team, we'll get it added if possible.

OK, let me check with the team if there's a newer version we can get you on. I'm intrigued that a specific device(s) cause this problem. Do you have any QoS, Geo-filter or Traffic Controller configuration that apply to these devices? If so, are you able to disable these when they're next over and see if the issue still occurs. Is there any option for you to connect these PCs to the modem via wired as opposed to wireless and check if the issue still occurs?

Interesting, thanks for letting us know. Have you upgraded to the full release version of iOS or are you using a beta version? Just to confirm, can you access the interface by going to 192.168.1.1 in your web browser?

Nice! Can't wait to hear your thoughts on it!

Not just yet, still testing and improving it. We'll likely post on our Twitter when we ready to share more info on it so that would be the best place to keep an eye out!

Hey! If you're using an R2 as indicated on your profile, then you'll need to go to either dumaos/ or 192.168.77.1 in your web browser on your phone. Let us know if you're then able to get to the mobile interface!

We are still working on it for the moment, as the new FIFA is coming out soon we're also doing captures on that and testing it with Ping Heatmap and Geo-filter, so rest assured we're still working on it.

Welcome to the forum! How did you factory reset the XR1000 exactly? Did you hold the reset pin on the back for at least thirty seconds, or did you do it from the Settings in the interface? What firmware version are you currently running on the XR? How are you testing your speeds exactly? Are you using the in-built Connection Benchmark or are you using a third-party speedtest such as speedtest.net for example?

OK, I think the best thing to do here would be to proceed with a replacement then. Could you please send an email over to [email protected] with your original order number and delivery address? Yeah you can revert the static IP you set now as well.

The solution here would be to put the DumaOS router inbetween the modem and the Google mesh, so the mesh connects to the DumaOS router through it's WAN port. The benefit here is that DumaOS' QoS is at the top of the network and should be able to control everything that goes through it.

Yeah so connect your devices to the Ubi network now. Are you able to connect a device to the R2 directly via ethernet? If so, do that, then access the R2 interface and disable it's Wi-Fi. You can then check that you still have access to the R2 interface over wired, then connect to the switch and verify the same is true. Assuming that's fine, the Ubi should also then have internet access and you should be able to get to the DumaOS interface from devices connected through there. Let us know how you get on, sometimes with these things it's just a case of working through a specific order.

If you hit 'Reset Allocation' and leave Share Excess enabled, those allocations won't be made unless an application/device is actually using bandwidth. Could you perhaps instead try adding each device you game on as their own rule in Traffic Prio. For the service on each of these rules, select 'Games Console'. Try playing a few games and see if the ping is closer to your idle ping.

We're currently in the process of testing a new version of Geo-filter, I don't believe we've tested it on Halo Infinite yet but I'll double check. It's working much better for many games though so we're hopeful Halo will also fall into that category!

Has that resolved the issue with Geo-filter now?

I see what you mean, displaying it's current IP address as well as adding the option to rename it from there would be handy! I'll add it to the roadmap and let the team know. Thanks Bernard.

Thanks for your feedback! We've actually been doing a lot of research and work into more accurate detection of device types. Doing this will also then enable us to give them all their own icons as you mention. I'm not sure exactly when we're going to be introducing that as there's still quite a few variables involved. Perhaps we can just make icons user changeable though, that's a nice idea. I'll add it to the roadmap!

Interesting! OK great, thanks for letting us know. Do give us a shout if you need anything else.

OK yeah that kinda makes sense then. I'd suggest leaving CC set to 100% for both sliders and just have Traffic Prio prioritising your gaming device. That shouldn't have any adverse affects and should help to keep the ping stable.

I believe that's expected at this stage, the requests made by the app look quite different to those from a browser. That being said, with the upcoming improvements to our DPI system, we should be able to classify these services much more accurately, so hopefully this would be something we could also use to improve traffic controller and block apps.

We'd need to monitor the backend of DumaOS and verify whether or not this traffic is actually being prioritised, or if it's just a front-end bug. Without Congestion Control, the effects of prioritising traffic would likely be greatly reduced, so I don't see any immediate reason to configure this way.

Not as yet I'm afraid, I chased up the developers about it this morning and they're going to see if they can allocate more time to debugging this issue today/this week.

Welcome to the forum! Thanks for posting so much detail with your issue, that's really helpful. Could you please go to Device Manager in the R2 interface, then from the three-line menu in the top left of the device map, switch to table view. Here, please send us a screenshot of the top table, named Port table. That should hopefully give us some more information.

Can you unplug ALL cables from the R2, then leave it for 15 minutes. After that, connect only the power cable and wait another 5 minutes. Then, connect one Ethernet cable from your PC to one of the R2 LAN ports. On that device, try going to 192.168.77.1 in your web browser and see if you can access the interface.

Thanks for the suggestion, I'll add it to the roadmap. Can you add a rule to Traffic Prio for your PC, then select 'Games Console' as the service. Disable all other rules in Traffic Prio then experiment with that and see if the game feels better.