Netduma Fraser

That's great to hear! Yes that's normal, if we can improve the amount of successful pings vs unsuccessful we will definitely do that.

Do this specifically 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.

If you can connect it via ethernet then yes you can do that. If you require PPPoE then yes you would then need to enter those details into the R3 to get a connection. Yes you can change the LAN IP of the router to that if you wish.

As above, you'll find all the necessary information via that link. Also comes with a 1 year warranty as well, starting from the date you receive it - not the date of purchase.

If that's the only thing that appears and you're in a game then yes that will be the server

What settings are you using specifically when that happens? Early next week I suspect for new firmware

Okay the team are looking into it currently and should have it resolved shortly. That's good to know thanks, we'll be looking into that as well.

It's likely that in the evenings/during peak times the game is trying to keep everyone more to their region, as more people are online the servers become more under load, adding high ping to that would result in a bad experience. Over the last few days it has occurred to me that it may be using a relay server which could be causing games to appear outside the radius. I'll have to have the team look into it.

That looks okay, when you get that message its for a legitimate reason it wasn't able to ping so assuming the ping in game is okay it should be good. Is that even with Steady Ping enabled and working? It should bring you more in sync with the game.

Both, we send our changes and they make a final build, that's what we've been waiting for I believe

Disable Private/Random MAC addresses for the WiFi on your phone and see if it works better then. New firmware will be early next week I believe.

I've sent you .23 via PM, you can upgrade from Settings > Troubleshooting, once complete I'd recommend doing a factory reset

We've fixed that for the next version I believe

Try this: Quit the application/game/client completely including from the System Tray 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.

As above, what CoD game are you playing and on what platform?

As others have mentioned above, it's not required and doesn't impact speed/range. This is the chip being used: https://www.broadcom.com/products/wireless/wireless-lan-infrastructure/bcm6756

NAT Type 2 is open so it's possible the game is a misreading, if you have the Geo-Filter enabled, disable it then start the game, does it appear open then?

Sounds like a potential power issue, do you have it connected to a power extender or direct to an outlet? If an extender please try direct to an outlet. Otherwise do you have another power adapter you could try with?

It depends what the cause is, thank you for the logs, I'll pass that onto the team. If its what I thought it was, change the lease time to 900 minutes. If that is the cause it should happen about 3 hours later so around 4am, I would think you're probably asleep then so you won't notice if it happens again.

I believe we did a Ping Heatmap update, if you resync the cloud and check

An authentication server wouldn't affect the quality of the game/the ability to find games, it just lets the game know that you're online, you have a legit copy of the game etc

Essentially ever since then we were waiting for firmware from not ourselves, it was outside our control, I realize it's annoying and it is to us as well. We're doing what we can to get it out as fast as possible.

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

Haha great to hear that! As above, its a server required for online play.

Anyone who reports issues that aren't a settings problem will have it brought up to the team, as I have done with this so it will be looked into, fixed and sorted via an update shortly