Netduma Fraser

Yes I'm pretty sure, the issue is that Ping Assist keeps reverting to it's previous state no matter how you try to set it, with a value set pre-upgrade that will be the value it resets to, after a reset the default will be 0 so it will prevent you using it

Added, please let us know if it continues after upgrading and a factory reset, make a new topic if it does https://forum.netduma.com/forum/151-netduma-r3-early-access/

Some servers can be mislocated on the map, if you provide the IDs we can correct them and that will help. I've given you Early Access so you can upgrade to the version there to see if there is an improvement https://forum.netduma.com/forum/151-netduma-r3-early-access/

I'll see if the team can test it, thanks for letting us know! If we can't we'll certainly do so at launch

I'll have to check regarding the tick rate of the kernel, I've no idea honestly and no one has ever asked that. To answer your other questions/points: It's not possible to SSH into the router Steady Ping won't work 100% of the time It's using codel with our own proprietary algorithm Yes QoS, Geo-Filter & Steady Ping can all be used at once

You'll need to factory reset, I think you've upgraded while you had Ping Assist set previously but as you've not reset its kept that Ping Assist value working but as it's not working to select it on this version you can't stop that happening without a reset

I'll let the team know, thanks for the suggestion!

Added, let us know if that resolves it for you

I've given you Early Access, upgrade to this version and it should fix it https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/

Double check the device you think your Xbox is has the same IP in the Device Manager as it does in the console network settings. If so, 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 It's essential the Geo-Filter is enabled before the game client or the game have been launched. If you change Geo-Filter settings when you're on the game then you will need to restart the game for those changes to take effect, otherwise it will use the previous Geo-Filter settings and appear not to be working.

Keep us updated!

I'll chase them and see when they can do it

Try it so the ISP router handles PPPoE with the R3 using DHCP and R3 in the modem DMZ, do you continue to get the same issues?

Disable Geo-Latency in the Geo-Filter settings, then restart the game and try again

Yes you can get them hours after - it depends how many entries are being written to it as they might not cover that time period but it should be fine.

You don't need to get the logs from a phone/a device that just had the issue, grab it from a PC next time it happens (don't reboot before getting it) and hopefully it'll have more information this time

Do a factory reset on this firmware, it shouldn't be needed but it is a big jump from the previous one so may help clear any remnants. How does the Geo-Filter become inactive exactly? Are you changing Geo-Filter settings while on the game? May be best to go back to DHCP/DMZ then for the moment while we continue to improve PPPoE.

Thanks for posting about your experience, your kind words and your feedback! Backing up/restoring your config is something I'd like to see as well and it has been requested before so it is on a list for potential integration in the future.

Are you getting just as high latency connected direct to your modem when playing? Did it start after changing any setting/your physical setup?

Did you get these logs directly after the issue as there isn't much in them and nothing really indicating a disconnect - did you reboot before getting the logs?

Probably more fixes that will help push us closer to the feature update but depends how it works out

IPv6 should be fine on any version really but DHCP & DMZ would be best if you still encounter PPPoE issues on that version

DHCP & DMZ would be my recommendation if you still have issues with PPPoE

It will be because you're pulling the power to restart, if you restart any other way it won't do that

What is the reason you're having to reboot the R3 exactly? Are you having any issues with IPv6?