Netduma Fraser

Nothing different than when it's on a long time frame, just happens more frequently - it's similar to leasing a car or apartment, the agreement is for a set amount of time, when that time is up you may move and have a new car or address, that's exactly what happens with the IP address, when that lease time runs out you'll get a new IP address, this can result in a brief disconnection while the change happens. By extending the lease time you hold on to your existing IP address for longer, thereby delaying the frequency of these connections. Now, what isn't clear at the moment is whether the DHCP lease you've changed is the correct lease or not. If it works then it will be, if not then it will specifically be the public IP lease which you'd need to contact your ISP to extend.

Hold the reset button in the back for 30 seconds, release, wait 4 minutes then access

I don't know what your setup is but potentially yes, extend it to a week for example and see how you get on

At least in this scenario your public IP changed but the connection should have only been down very briefly, see if your ISP can extend the lease time on the IP and that will help

I'll let the team know the cloud needs updating and we can see if it works after that. You can't disable the features on the router that way

By back out to windows, do you mean the game is still running in the background? Try with the circle radius rather than custom and try again

Added

Great to hear, thanks for the update!

What firmware are you on currently? May be beneficial for WiFi to downgrade and see if performance improves. Could you expand on this? "As for efootball, the router clearly has no impact unless you know the server you are playing on. " Disable telemetry in Settings > Troubleshooting and that will stop the error - it's no longer an aspect of the router so there is no need to keep it on

Okay well you don't need to change anything specifically on the R3. It would be a good idea to put the R3 in the Eero DMZ though to ensure you get an Open NAT

Are you actually experiencing any issues with the upload at all? It may just be due to being a slower upload the test reports high bufferbloat regardless

Yes please I can't see how that's the case, it's showing a connection to it without an allowed circle around it so it's not blocked and can be connected to when you have the Geo-Filter off. I can pass it on but I don't think that's it. Resync the cloud on Heatmap and see if it appears, if not I'll pass it on

If the R3 is behind the mesh then only devices directly connected to the R3 can use the features/be controlled by the R3. I'd suggest having it the other way around for the best of both worlds, i.e. Modem > R3 > Mesh and no settings need to be changed then

Have you got Ping Assist enabled? Are you enabling the Geo-Filter when you're already on the game or changing Geo-Filter settings while on the game?

Added - https://forum.netduma.com/forum/144-netduma-r2-early-access/

I'd suggest having a look at support.netduma.com, there are also many guides on YouTube, any questions do let us know.

Wait 1 minute and then refresh the page and the cloud will have applied. It can't be the cloud, as you mentioned, with the Geo-Filter disabled it still occurs, that would only be at fault if it was with the Geo-Filter enabled. The R1 is over a decade old, it's not possible for it to have the latest and greatest software

Ping Heatmap? It should be there. If you do the above does that work?

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? Have you entered 1Gbps into the router? How have you setup Congestion Control? How have you setup SmartBOOST? Are you connected via ethernet when testing?

Okay that's good thank you. Set the IP of the R3 as static/reserved on the ISP modem/router, then reboot the modem, wait 2 minutes, reboot the R3, wait 4 minutes then see if it happens again please

You shouldn't need to select anything else. Not specifically that I am aware of but as long as you can get an Open NAT now through a console/on a game while connected to the R3 then you're good

Please provide a screenshot of the R3 WAN Settings page

Copy the WAN IP from the R3 WAN Settings page and enter that into the DMZ section on the ISP router

Yes please try that but also set the R1 WAN IP as static/reserved on the ISP router so it doesn't change and make the DMZ invalid. You can keep UPnP enabled

Did your ISP router/modem disconnect at the same time? Are you using PPPoE?