DynDNS doesn't get updated on WAN ip change

[steven@…]

since september/2.3.0 the dyndns service does not work stable anymore; ez-update service just... goes away after 24h and will thus not notice any ipupdates anymore and update my dyndns service anymore I have to manually restart /etc/fonstated/RestartDDNS and report the process it wants to kill to not exist...

within 48h I will have to do this again

[matthijs]

Could you check that this is also broken with 2.3.6.0 (Gari) on 2.0n?

[steven@…]

yes also in 2.3.6 it's broken... if your fonera 2.0n doesn't get rebooted within a week it is inevitable that the dyndns service stops to run and will not update your ip. ADSL sessions have an urge of getting a new ip every 36h (ppoe session timeout)

[steven@…]

Dyndns plugin doesn't work anymore when in Bridge mode (fonera 2.0n using 2.3.6.1) ./etc/fonstated/RestartDDNS will try to perform uci -P /var/state/ get network.wan.up but network.wan.up doesn't exist anymore in bridge

quick fix: uci set network.wan.up=1 uci commit

[steven@…]

and another addon to the quickfix:

uci add fonstate dyndnstimer uci set fonstate.@dyndnstimer[-1].action="/etc/fonstated/RestartDDNS > /dev/null 2>&1" uci set fonstate.@dyndnstimer[-1].period=86400 uci commit

to keep it restarting RestartDDNS every 24h as it seems to not stick

[matthijs]

I've reported the DynDNS in bridge mode issue reported in comment:5 in a separate ticket: #998 (since it is a separate issue that should be trivial to fix).

[anonymous]

Any solution, I have a Fonera 2.0N 2.3.6.1 and the dyndns not updtade when ip changed.Thanks a lot.

[matthijs]

As part of the upcoming 2.3.7.0 firmware release, we're reviewing old open tickets to see if they are still relevant, which is why you get this response now.

2.3.7.0 rc2 includes different DDNS software, so it is likely this bug has been fixed as a side effect.

If this issue still occurs with the  2.3.7.0 rc2 firmware, feel free to leave a comment here so we can further investigate.