Netduma Fraser

The log wouldn't solve the issue, if you provide it to us it will give us more information (hopefully) about why it may be happening

Thanks for letting us know, the team are looking into it

They are designed to be always on so that could be a contributing factor, you could disable the WiFi from the WiFi settings

What happens exactly they can connect but don't have internet? Have you split the bands and connected them to 2.4 or 5GHz to see if that works?

What are your Congestion Control/SmartBOOST/Geo-Filter settings? Is this the ping on the Geo or in game?

It depends how you have it set, in some cases that could happen. Try this: Disable GeoLatency Disable PingAssist (set it to 0,0) Enable Strict Mode Disable Fast Search Use the simple mode instead of custom mode for the radius/area 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.

Do a factory reset when you have time as it'll be a significant change from previous versions then follow the same steps. It's possible that the IP of the router has changed so if you set it in the DMZ on your modem it may not apply until you update the IP there.

Added

Use 192.168.1.1 to access, does that work better?

Correct yes. However, it's not necessarily a bug if you get a game outside your radius with Geo-Latency on, that can happen, it just means that despite the game knowing putting you on that server is going to give you a bad experience it does it anyway. So we're adjusting parameters to find the sweet spot where that happens very little. There is likely a NAT server being blocked by the Geo-Filter when that happens, have a look at the map when you do the test and allow the server that gets blocked.

Understood, 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 better.

When a new firmware arrives we will post it in the forum like the .41 firmware. You don't need to repeat the issues you're having, once reported the first time the team can take a look at it. Thanks for the theme report, haven't heard about that. Are you turning the router off and on each night?

Give it a reboot and you should be able to access then, is the WiFi still working once you do that?

That's a shame, we're still looking into it, it doesn't seem to be a straight forward issue but we'll definitely get there.

Are you both on the .41 firmware?

For the phones/tablets, if you disable the Random/Private MAC addresses option for the WiFi when you're connected does it continue to happen?

Are you getting a worse ping than mentioned as it's not a bad ping at all really. What is the model of the modem/router the R3 is connected to and how have you set that to ensure all traffic flows to the R3? E.g. R3 in its DMZ, modem/bridge mode. Are ALL devices connected to the R3?

I don't make decisions on policy or firmware so I'll pass it on, I've responded to your email.

Routers are generally very low power and are designed to be on all the time so I would suggest as the others have to leave it on. You could disable the RGB though every night as that would save some power.

I'll add it to the list!

They're both blocked there unless you zoom out and see anything else being allowed?

Have you followed all the steps you did previously? Did you factory reset after the update?

Correct/we made fixes and sent to get it built again

That's a good question, it's been a very very long time since that firmware has been used, from memory it would be the latter

You'll need to sign up here first: https://forum.netduma.com/topic/39415-introducing-early-access/