Netduma Liam

OK, thanks for letting us know, we've got a new firmware coming out very soon for the R2 so that should definitely help with the problem!

OK, glad to hear it was able to get through the boot process properly then. I believe it's more a case of residual power draining rather than heat, although it's never a bad idea to give it a little more ventilation! Let us know if you run into any other problems with it.

OK, thank you. Could you please try Fraser's last suggestion and see if that helps?

I can certainly understand your frustration, we understand that screenshotting your config isn't a feasible solution, more just a suggestion to help a user in the meantime. I'll also raise the problem with the team again to bring it to the forefront, I'll get someone to replicate it and investigate why it occurs from a backend perspective.

You can save device information and restore that on the R2, there isn't currently a way to save and restore network configuration however. I've responded to your post in the other topic, though if you'd like to troubleshoot the issues you're having it may be best to open a new topic.

To clarify, are you experiencing this on an R2 or on an XR500? What firmware version are you currently running?

Not sure, we found a bug while testing it so the devs are currently working on fixing that now. Once that's done we'll re-test it. After that, it'll go out to beta testers first before we can fully release it.

Righto, let us know if you run into similar problems again!

Were you able to get a recording of this? Are you able to provide the ID of the peer?

OK, thanks for the update, I'll pass that across.

Cool idea! In the mean time you could probably just unplug the WAN cable and reconnect it again? Unfortunately there isn't a bridge mode currently available on the R2.

Thanks for the update. The dev looking at your logs has been unwell recently but I've checked in again today so we'll get back to you when we know!

We've been working super hard and are now testing new firmware, it shouldn't be too much longer before we can release one!

It's not possible currently I'm afraid, what's the reason for needing to do this?

You can either check the R1 Support forum, or eventually we'll also put it on our Latest Firmwares page once it's full release. http://support.netduma.com/support/solutions/articles/16000091217-latest-firmwares

Thanks for posting this, I don't believe it can be caused by having too many clients connected but we are working on porting a hotfix for this issue over to the R1, so that should resolve these problems for you.

We're aware of this and we're looking for a permanent solution to the problem, it's caused by Activision updating their server information every day, it's not your router. I don't have an ETA for when it'll be fixed but we're working on it!

Let us know how you get on! That's interesting, do monitor that and get back to us if it becomes a regular occurance.

Honestly, not sure, I think back when we designed Geo-filter there could've been an issue displaying these IPs so publicly, but as Fraser said they're freely displayed in Ping Heatmap if you wanted to see them.

Awesome, thank you. It's just a unique way of identifying a connection, it's calculated based off of an IP address we can work out on our side.

OK, next time this occurs and you click on the peer and check their ID? This will let us know if it's the same player or if it's just appearing in the same location.

Ah OK - thanks for explaining. How do you know that it was the same player? Was their icon on the same place or did you check their ID?

Could you let us know what it is you're looking to block? Is it a specific player, such that you don't match with them again?

OK no problem, let us know if the problem persists with IPv6 disabled and we can look into it further.

OK yes please do disable IPv6 again and let me know. Are you now able to access the interface again when it disconnects?