Netduma Fraser

I know we started dabbling with a reporting system on the interface, I'll make a request for that again but we'd always have to double check reports before making them permanent

Sign up here: https://docs.google.com/forms/d/1J6_HsakqnRL6GG3nT-3BGuZkakqsikkn7cFNsSY5hz4/viewform?edit_requested=true and when available you'll get access

Get it so it appears like the screenshot above, then disable the filter, does that then allow you to connect to that server faster?

That's brilliant thank you, I will pass it onto the team to get the locations corrected.

Okay thank you, I think from what you said it's an issue that has been fixed for the next version so shouldn't happen again once that is available. Give the devices having an issue a static/reserved IP and see if that helps please

If you let us know the issues you're having I'm sure we can help

Set the download/upload Congestion Control to 70% each and see if that helps please

We haven't added it yet but when we do we can add it to the other routers via a cloud update

That's actually the part of the QoS page I'm least interested in, Congestion Control & Traffic Prioritization if you could show how they're setup please.

That would be Geo-Latency most likely yes. If you provide the ID I can take a look. That would definitely be mislocated then! For these, none of them are Oklahoma - is that where they all appear? 2 Chile, 2 Spain & 1 Texas

That all looks fine and like it is working, it looks like you're connected also but it doesn't convert to a game? Will it continue to show like that for the entire search?

You should have a confirmation email already, it'll likely be in your spam/junk folder. Once shipped on Monday you will receive a tracking email

I've seen this before, I believe it's showing 160 on the R3 as the IP for the server has some hops on the way to it timing out and therefore inflating the ping but it has been reported that when this happens it does play more like 160 than the low ping so best thing to do would be to add that server to your deny list so you don't play on it again.

When you launch the game initially have a look at the map, do you notice servers outside your radius all showing up with a blocked icon?

I think as above it'll be better in the next firmware but make sure the R3 is in the DMZ on the upstream router and it may help

Yes that's correct, try that and see if it helps. Otherwise, could you provide a screenshot of your QoS page please? Also, what is the model of the modem/router the XR is connected to and how have you set that to ensure all traffic flows to the XR? E.g. XR in its DMZ, modem/bridge mode

Did anything change in your setup or was there an update prior? You are on an old version which won't be helping, upgrade to this one here: https://forum.netduma.com/topic/53938-new-r3-firmware-4041/

What happens exactly when you try to login but you're unable to? For the disconnects we believe we know what the issue is and it should be fixed in the next version. In the meantime, could you in DHCP settings, set the DHCP range to start at .50, then assign reserved IP addresses to devices between .2 & .49 so they're out of the DHCP range & apply. Also set the DHCP lease to 10000, apply, reboot from the interface, wait 4 minutes and see if that stops the disconnects.

Are you changing Geo-Filter settings while you're on the game at all?

It'll probably be in the next firmware or the one after that. Can you connect using the credentials instead?

Have you updated to the latest app update as this should be fixed now. I don't see an error either from your screenshot, doesn't look like you've tried to login there

We believe we know what the issue is and it should be fixed in the next version. In the meantime, could you in DHCP settings, set the DHCP range to start at .50, then assign reserved IP addresses to devices between .2 & .49 so they're out of the DHCP range & apply. Also set the DHCP lease to 10000, apply, reboot from the interface, wait 4 minutes and see if that stops the disconnects.

Have you set a different DNS on the devices themselves?

Are you trying to play together or separately? In WAN Settings set NAT to Open and then check again please

The focus is ensuring a low ping, so we can't guarantee better hit detection etc though it should be better on a low ping. We will add support for it yes but as I mentioned if you don't have many servers around you then it may not be as helpful to you.