sentinel-dynfw-client fails to detect wan ip rollover and remains stuck at previous wan ip
TOS 3.11.1 stable
It is not uncommon for ISP providing pppoe to rollover ip assigned to their client at a certain frequency. It appears that the
sentinel-dynfw-client fails to detect such ip rollover and remains stuck at previous ip instead. Which likely can cause all kind of unintended consequences, e.g. the client running
sentinel-dynfw-client not being protected or the other ISP customer having assigned now the previous ip facing issues or even the ISP blacklisting the sentintel backend 184.108.40.206:7087 due to misbehaviour.
Only after manually restarting
sentinel-dynfw-client the current/correct wan ip is picked up.