Flint 2 with latest v24 gline firmware. The DDNS stop working if reboot is done

[MatteoIta]

Hello.

I am using a GL.iNet Flint 2 with the original GL.i.Net firmware, updated to the latest available version (v24). I’ve noticed that after rebooting the router, I must manually log into the admin interface and stop/start the DDNS service. If I don’t do this, the WireGuard VPN is unable to resolve the new public IP address.

Even after 24 hours, I can't connect to the router via wireguard if I don't stop and start manually the ddns service

Shall I have to set something different?

Thank you

[juane]

I have the Same issue since upgraded, but each 72-96 hours.

[gfondeur]

This being going on for a min, we on the same boat DynamicDns not refresh IP automaticly

[will.qiu]

Hi

We have also identified this issue on our end.
Our development team has already implemented a fix, which will be included in an upcoming release.

In the meantime, please refer to the workaround described in the following post:

DynamicDns not refresh IP automaticly

We have also reproduced this issue locally and will have our R&D team investigate it. As a temporary workaround, please add the following lines to /etc/rc.local for now. [image] sleep 10 /etc/init.d/gl_ddns start

[MatteoIta]

Thank you very much, I tried and the workaround works perfectly.

I will wait for the new firmware to be released.