Netduma Fraser

Thanks a lot for the logs and remove access, I'll pass this on to the team to look into tomorrow

It can work, if it doesn't work at first keep retrying, if it continues to not work then it maybe your device is incompatible - what device are you trying to connect?

Try this: Quit the application/game/client completely Remove device from the Geo-Filter Resync from the Geo-Filter Map menu Re-add the device to the Geo-Filter Set up the Geo-Filter how you like Wait 2 minutes Boot up application/game/client Then see if it works.

Thanks for the logs, we'll take a look. No WPS on the interface, there is the physical button on the router

Likely the latter but as it would be closed requests wouldn't be considered - we'd aim though to get it into Early Access as soon as possible after that though so we get more testing done

Great, do keep us updated! Yeah it is a bit strange, perhaps the port isn't waking up correctly, the team will check

Yeah I think that's probably it as we have seen some issues with devices reconnecting in the past when in that state - I'll get the team to try and reproduce it

I was under the impression WPS wasn't working at all but apparently it's working about 70% of the time so if it doesn't work right away try again and it should work. If not it may not be compatible but we will be doing more work on it to improve its reliability.

That wouldn't be possible unfortunately

We don't give out any ETAs and there is no beta currently, it will go into closed beta testing soon

Ahh brilliant to hear, glad it's all better now! Do you have access to the interface when it disconnects? Could you get the logs from here when it next happens please (it should work without access) http://192.168.77.1/cgi-bin/logs.txt What device are you trying to connect with WPS? It is available on the app, are you definitely on the .219 and the latest app update?

Would you be able to make a video of it happening please? This would allow us to pass it on the devs and easily reproduce the issue

I'd go with the R3 personally, it's direct from us so faster updates and it has DumaOS 4 which the XR range won't get

That's very bizarre, the devices it happens to most often, are they left in an instant on/standby state at all?

Are you using PPPoE, VLAN or DHCP identifiers? If you do a speedtest do your speeds decrease (with bypass disabled)? Have you got your expected/paid for speeds entered correctly?

Thanks for the chase, I'll get him to do it this week.

Disable GeoLatency Disable PingAssist (set it to 0,0) Enable Strict Mode Disable Fast Search Then restart game or wait 10 minutes (in the lobby in the game). If that doesn't work, reboot PC/Console and it should work then.

It's been awhile for this update honestly, I couldn't provide an ETA really but it shouldn't be much longer

It should be disabled by default but yes in Settings > Guest Network

It wouldn't affect the internet but does it let you into the interface if you pressed those buttons? Disable IPv6 in LAN/WAN and see if the disconnects become less frequent.

Thank you for this I will pass it on - does it reconnect when that happens? If you press retry or continue anyway can you get into the interface?

Disable IPv6 in LAN/WAN and then try again please

Thank you for the suggestions, I will certainly pass them on, there has been some discussion on the third point but as for the rest I'm not aware personally of any plans for it.

If you have it set to Auto that'll be why, make sure it's set to Always, otherwise disable Speed Test Bypass and try again

Don't block that server, it is a authentication server required for online play and it's likely that blocking it has contributed to your issue of finding games. If you've done this for any other servers remove the blocks and see if you get games more often. Thank you for the remote access, unfortunately they'd need to access when the issue is happening, with us being in the UK and them already having a busy schedule it'll be hard to sync up. When it does happen if you could get the logs from here: http://192.168.77.1/cgi-bin/logs.txt (it should work even if you don't have access to the interface) it will provide more information so the team can figure it out.