Netduma Liam

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?

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.

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?

Sorry to hear this, I've responded to you in the other topic you commented on. If you wanted to return the R2, email us over at [email protected].

Awesome! Thanks for letting us know

I've sent you a PM

Welcome to the forum! Yeah it's back on Google Play Store, it never went anywhere on iOS.

OK, looks to me like you've got CG-NAT there, if you check out the bottom of the guide Fraser sent you, I'd suggest contacting your ISP to see if they can opt you out of this.

OK great no worries, I think I've responded to your offline message this morning so let us know if you need anything else!

Could you please take the AT&T out of passthrough mode and instead put the R1 WAN IP in the AT&T DMZ. Then make sure the WAN IP for the R1 is reserved from the AT&T interface so it won't change again in future. You may need to reboot the R1 after making these changes for your NAT type to then appear open.

OK, that will be the reason then. QoS is limiting your speed in order to ensure priority devices get enough bandwidth, you can set this to Auto-enable if you want to have your full bandwidth when not gaming.

Adblocker relies on some of the features of QoS for inspecting traffic, in theory it shouldn't be too difficult to have Adblocker work independently of QoS so that's something we aim to do in future.

Can you both please go to the three-line menu in Ping Heatmap and hit Resync Cloud, it should be fine for you then.

Thanks for the feedback, glad you're enjoying it!