Netduma Fraser

As above, still on track for this week

The router has its own built in firewall so it's perfectly safe. It would only be a security risk if you then put your PC in the DMZ on the R3 for example.

Reboot the speedport, wait 2 minutes, then reboot the R2, wait 4 minutes then check to see if you have internet

But how have you entered that on the router specifically?

Is Traffic Prioritization prioritizing anything at the time and do you have the Congestion Control percentages lowered? If so that is expected behavior.

Could you make yourself accessible again please, also disable IPv6 in LAN/WAN and then PM me your public IP please? Post here when you've done that

As above, are you making changes while on the game? Any Geo-Filter settings should be made before you boot the device/game

It's likely something is being blocked on the map when that error appears, adding it to the allow list should then prevent it - you may need to do it a few times in case they're using different servers

Are you accessing the interface using HTTPS? If so use HTTP and see if that works. Also disable any browser based Adblockers. Are you using Armor?

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.

Exactly as above, will be even better!

As of this morning when I asked it's still expected this week, I'd estimate tomorrow afternoon/evening probably

New firmware is expected this week

As above, give that a try and see if that resolves it

It's an authentication server required for online play, it appears the game server is actually within your radius. The auth server will not affect your ping/game experience at all.

As above, instead of me sending it to everyone the firmware is stable enough to just allow it to be downloaded by anyone

Great to hear, CPU issue will be resolved for the firmware coming, still on track for this week I believe

That's great to hear, thanks for the update!

That's a very strange one, surely the phone locking wouldn't have caused that but I will pass this onto the team so they can try to reproduce it, thanks for the report!

Glad to hear you got it sorted. To answer your question about why it's not showing on the router, it was a firmware made on the last day before the holidays, had there been any major issues with it and we made it available for everyone there would be no one in to fix it for 3 weeks and would be a major disaster. So I just provided it to people manually over the holidays and monitored the feedback. All seems good so I put it up there on the latest. I suspect the team won't want to push it when everyone is expecting new firmware now.

Do you have the console set to turn off to an instant on/standby mode or is it being shut down fully and turned on fully each time?

There aren't any beta versions available for it unfortunately

I don't think the plan will be to wait until everything has been fixed, more likely it will come incrementally

Thanks for the suggestion, I'll add it to the list!

Set it up so that it is in bridge or modem mode, you can also use the DMZ. Copy the WAN IP from the R3 (found in Settings > WAN) and enter it into the DMZ function on the USG. You should get an Open NAT then.