Netduma Liam

The same/similar settings are also enabled by default in the Wi-Fi settings. If you view the options/settings on the R2 Wi-Fi network on your Apple device, you should be able to disable 'Private Addresses' and the other similar sounding settings there (I can't remember exactly what they call them now). Can you try disabling those and see if that helps? Apologies if those are the settings you're referring to having already disabled above.

Welcome to the forum! Generally speaking, most games only use purely server based matchmaking, or peer-to-peer matchmaking. So this hasn't been something we've needed to implement in the past. If you're seeing a mixture of the two, it may be that some servers are being misclassified as peers. We're planning some improvements to Geo-filter which will mean the representation of peers and servers will change, so this wouldn't be required. I don't have an exact ETA for this change, but we are working on it currently.

OK, once the new connection is installed, can you please factory reset the R2 and set it up fresh with the new connection? Then set up QoS how you like it again and you should be good to go! Hopefully that base ping comes down a little more with the new connection.

Could you clarify which router you're using specifically, the R1 or the R2? Which firmware version are you currently running? Do you have ALL devices on the network connected to the DumaOS router?

Is this just over Wi-Fi, not over wired? What device were you playing on and what game specifically? How far is that device from the R2? We are aware the Wi-Fi on the R2 isn't as good as we'd like it to be so it's possible that's the problem. Of course gaming over wired is always our recommendation.

In general, the Wi-Fi performance of the R2 will not be as good as the XR500, the hardware and drivers aren't quite as good as they are in the XR. If the coverage with the R2 isn't good enough, you can connect the XR to the R2 and put the XR in AP mode from it's settings. That will make the XR behave purely as an access point (AP) with no other settings enabled, extending the range of the R2s Wi-Fi. Let me know if you have any other questions.

Thanks for that, that's really helpful. Were all Ookla tests run from the Macbook? Are all devices seeing this much of a reduction in speeds? Do you know if your ISP requires you to use PPPoE, VLAN or DHCP identifiers in order to get connected? If you're not familiar with these terms, it's likely you don't require them.

Which firmware version are you running on the R2 exactly?

Welcome to the forum! Could you perhaps try going to Settings -> Setup -> LAN Setup and change the minimum DHCP value to be 100. Then, reserve IPs for each device connected to the XR. Give them IPs from .2 to .99 so they're outside the DHCP range. Let us know if they still have connection issues after that!

Is your network simply setup as Internet -> Modem -> R2 -> Connected devices? If not, what's your exact physical setup?

It's on our roadmap, but there's a lot of overhauls happening around these features so it won't be implemented until we've worked out more of how we're going to improve the rest of these features.

So what problem is this causing specifically? The R2 doesn't have an IPv6 address? The PC connected to the R2 doesn't? There isn't a DHCP relay option on the R2 just yet I'm afraid.

I see, unfortunately there won't be a way that the PC can have an IP from the main router, but still be controlled by DumaOS. What problem is this causing you specifically? The R2 will still have an IP from the Main routers subnet, so your PC should still have access to any other resources on the main router's network.

Hey, welcome to the forum! I responded to you on Twitter, but I'll also respond here for anyone else wondering. The CoD servers seemed to change last night, so Ping Heatmap is now out-of-date. We're updating them now, you should see all the servers back later on today!

Deep Packet Inspection. In short, in what DumaOS uses to identify the different applications/games are running. Each application usually has something unique about it's traffic, we teach DPI what to look for and it can then identify that traffic and do what you like with it.

Which firmware version did you upgrade to specifically? Since upgrading, can you please now factory reset the R2 to ensure you're starting from a clean slate? There's likely been some big changes from the firmware you were on to the one you're one now, so a reset is required to clear out any old low-level code that could be left over from previous firwmare.

I would suggest setting the bandwidth speeds in QoS to be what you get through your speedtest, ~800mbps. Then, adjust the sliders down to 50/60% roughly and set Congestion Control the Auto-enable. That should allow QoS to work properly with your network.

I believe the setting you're looking for can be found in Settings -> Setup -> WAN Setup -> NAT filtering. You can make sure that's set to secure. In terms of firewall settings, there's not too much you can change from the interface. He could sign up for Armor for peace of mind if he'd like to, certainly don't have any further communication with the caller he spoke to though.

We were looking at implementing a lower value to Ping Assist, so you can set a ping range, meaning Geo-filter would block servers with a ping below your minimum value, and above your maximum value. In the mean time, the best solution would be to use Ping Heatmap to find which servers are around the ping you'd like, then use Polygon mode to set polygons around those locations.

Are you having the same problem with your R1? Or are you also using an XR router now?

What do you mean by two ISPs? Do you have two separate providers that you pay for seperately? Or are you referring to your two routers (Main router and R2) as ISPs? The optimal solution would be to have the R2 at the top of the network so all devices go through the R2 at some point. That would allow you to control everything on the network with QoS use Geo-filter too. The R2 also has a built in domain-based adblocker, so you may not need the PiHole then either.

Interesting, thanks for letting us know. Can you perhaps try reproducing the issue a couple times and then download a log file from System Information?

Interesting, so does everything work perfectly fine if QoS is disabled completely? Have you setup Adblocker at all since getting the R2? Have you for example added any custom domains? Do you have any rules setup in Traffic Controller?

Das gleiche Passwort, aber die SSID ist anders? Ist das korrekt? Haben Sie das WLAN am Hauptmodem deaktiviert?

We've got a new update for DPI out that's trying to help with this. Update to the latest firmware, then factory reset your R2. Atfter 5 minutes, complete the setup wizard again and setup QoS/Geo-filter/All your other setup how you like it. You can then go to Device Manager -> Click the sub-menu in the top left of the map -> Hit Resync cloud and things should be feeling better.