Netduma Liam

Can you clear your browsers cache now that you've completed the update and see if it works after that?

I'm pretty sure the issue actually sits on the WAN side of the R2 so we are looking into how we can resolve this, unfortunately it's quite a complicated issue (as always seems to be the case with IPv6). We'll keep at it, but in the mean time you'll need to use IPv4 with the Xbox.

If you click the three-line menu in the top-left of the logs panel, you can download them and send them over to us. That'd give us more info and may contain entries to point us at the issue.

Could you download a copy of the log file from System Information, then send that over to us? Ideally shortly after the issue occurs so we can find it in the logs if it's there.

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?

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?

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!

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.

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.

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!

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.

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! When this issue occurs, can you please go to Device Manager, then click the three-line menu in the top left of the map and switch to table view. Could you please then send over a screenshot of the top Ports table? Also, if you completely disable QoS from the three-line menu in Congestion Control, do you speeds return to normal?

So you're not seeing any icons on the map at all? What device are you playing on? Could you double check that device is definitely connected to the XR1000 and it hasn't connected to the upstream router/modem? This may happen if using Wi-Fi. Could you please provide a screenshot of how you've got Geo-filter configured exactly?

Hey, did you by any chance remove the ListenPort field from the config file? While trying to reproduce your bug, I've noticed ListernPort is essential, otherwise it'll throw this error. To provide an update: We've successfully reproduced your issue internally and we're now working on fixing it with a developer.

OK, let me raise a ticket with our VPN dev and see if he can find any reason as to why that's not working, it looks perfectly fine to me. I'll get back to you.

Have you posted your message here from a device connected directly to the R2? Do you know the model of the Arris? Is it a router/modem combo (Has Wi-Fi) or is it a pure modem (Does not broadcast a Wi-Fi network)?

Yeah looks like the R2 has given it an IPv6 address but it's not being used. Can you confirm if you've ever had an IPv6 address on the Xbox when connected to the R2?

Does it work again briefly after you reboot? If not, can you paste the config file here? Make sure you remove you remove the private and public key before you paste it.

To clarify, you've previously had IPv6 on the Xbox when playing through the R2? Is that correct? In Device Manager, click on your xbox, does it show as having an IPv6 address there?

I don't appear to be able to access your R2. Have you posted your message here from a device connected directly to the R2? If so, could you please see if you're able to access your modem's interface and put the WAN IP of the R2 in it's DMZ? Let us know if you have any issues doing this and also let us know the exact make and model of the modem if possible.

Are all devices losing connection or is it just specifically devices that are connected via Wi-Fi? Are you able to access the DumaOS interface when the disconnection occurs?

It should still show in the logs. You could perhaps experiment changing the DNS server to a different DNS in the country you're VPNing too. Otherwise if you could grab a log next time you come across the problem that'd be really helpful.