Netduma Liam

So in it's current configuration, are you able to get two XBOX's online both with Open NAT, or only one? Could you share a screenshot of the port forwarding rules you've setup by chance?

That's fine, we wouldn't expect it to. The VPN is being applied on the router, not on your PC. Everything in the network connects to the router as it did before, but as soon as it leaves the network your traffic is going through the VPN (Only the devices you've added to the VPN Traffic panel).

The servers shown in Ping Heatmap are all the servers that the game client looks for when it boots, so it's possible the information online isn't up-to-date. That being said, the servers listed in Ping Heatmap look like they need updating so I'll speak to the team and they'll get that done.

That is very strange. Were these reboots in quick succession or was there at least a few minutes between each reboot? Have you since managed to successfully get DumaOS to load?

Welcome to the forum! Could you please create a new topic and be sure to include the following information: If you hold the reset pin on the back of the R2 for thirty seconds, then leave it for a few minutes, are you able to get to the DumaOS interface by going to 192.168.77.1 in your web browser? Do you still have internet access through the R2? Are you using the original power adapter that came with the R2? Is it connected to a wall outlet or is it connected to a power extender/power strip? Once you've created the new topic, we can focus on your issue and troubleshoot it further with you.

Just to double check, have you factory reset the R2 since getting the new line? If not, I'd suggest doing so if possible. It's always a good idea to set the R2 up fresh when it's on a new line. Give that a try if you haven't already and check if that improves your results.

Welcome to the forum! Have you added any devices to the VPN traffic panel on the right hand side? If not, you'll need to do this to route the device's traffic through the VPN. Start with the device you're checking the location on, then you can check again and confirm that the location has changed.

May be a caching issue in that case. Perhaps try clearing firefox's cache. It may take a little longer to load the pages initially but once re-cached it should be all good again!

Yeah you should be able to access the interface by going to routerlogin.net. When this issue occurs, open a browser and see if you're able to access routerlogin.net from your web browser. If you are, can you think of any recent changes to the network or to Windows around the time you started noticing this problem?

What device are you downloading an update from? How is that device connected to the R2? You'll notice this affect all traffic that's not prioritised in Traffic Prioritisation, so if it's affecting you watching Twitch, re-enable that rule in Traffic Prio. Just bear in mind that if you're gaming and watching a stream at the same time, the two will both be prioritised and may affect one another.

Excellent, great to hear. Thank you for letting us know.

You've got Twitch prioritised in Traffic Prio, disable that and it should stop affecting your game. Also, make sure you set your Congestion Control sliders to ~70% each. It should all perform much better after that.

We don't have an ETA as yet, we're making some substantial changes to how Geo-filter works. Our testing has proved very promising, but it's still ultimately in development so I can't yet provide an ETA.

Thanks for letting us know, to be honest it's hard for me to deduce exactly what the error was, I need the devs to tail it back and see what initially caused it. There are an excessive amount of entries on DHCP, which may or may not be a hint. You've got a lot of devices on the network I see, so it'd be unreasonable to ask you to test reserving IP addresses for all of them. If you have spare time and are curious, feel free to give it a try, just make sure you give them IPs outside of the DHCP range. However, there's no guarantee this will be the solution so don't worry about it too much. I've found the latest crash in your logs and updated the ticket for the devs, I'll let you know when I've heard back!

Thanks for letting us know, I've found the error in the logs and it looks like it should be pretty useful. I've made a ticket with our developers for them to look into the issue further. I'll keep you updated.

Maybe it's struggling to resolve routerlogin.net. Is it any different if you go to 192.168.1.1?

OK not to worry, let us know when you're available and we can pick this up again.

Now that's interesting. Did you factory reset the R2 since getting the new connection setup? If not, could you please do so and then check if these features are able to work properly again? Ideally the ISP equipment would be set to either a modem/bridge/passthrough mode, or the R2 would be in the DMZ. If they are not willing to make these configuration changes for you, we could also potentially look at trying some port forwarding, but that's far from ideal.

We've made a change via a cloud update, could you try re-syncing again and see if it updates?

That's odd, maybe you could try adding a rule to Traffic Prio for the new device and just have it prioritise all traffic from it. It may then be able to work with QoS in your usual configuration.

Is there any excessive CPU usage when you're trying to transfer over Wi-Fi?

It's finally home. Thanks for letting us know, could you please grab the R2's WAN IP from System Information, then put this in the DMZ of the ISP router. After that the Xbox's should have an Open NAT.

You don't need internet access to get to the interface, it runs locally on the router. Though, if the router is unresponsive you may not be able to get to the interface. Let us know next time it happens if you can get to the interface from either a wired or a wireless device.

Welcome to the forum! Thanks for the details, that's really helpful. Could you please try completely disabling QoS from the three-line menu in Congestion Control, then see if the VRROOM device has any further issues?

Since deactivating it have you tried re-syncing cloud again? If not you'll need to do that to get the latest information.