Legacy DDNS retiring without a replacement for URL callbacks?

[franco]

Apparently the new ddns plugin is not triggered by newwanip but rather spams the DynDNS provider with updates every 5 min (300 sec iirc). That was apparently not the case with the old plugin. For the Python script the default in the GUI is one update a day at 00:00.

It does what you set for "Interval" after all, although technically it says it checks for an update and only updates if one was found so I'm not sure what your analysis is based on saying it spams the provider, unless perhaps the provider does not accept the new IP in which case it needs to retry...


Cheers,
Franco

[chemlud]

I had a look in the log for the new plugin and saw many rejected update events this morning (with 23.1.1 latest), which I don't see with 22.7.last.

I can confirm the update attempts from the log of my DynDNS provider every 5 min saying "OK, no IP change" for the new ddns plugin in OPNsense with 23.1, but not for 22.7 OPNsense.

[franco]

Some people suggested the local cached stats might be wrong in 23.1 but I'm unsure why (PHP 8.1 issue?), which could produce this outcome.


Cheers,
Franco

[chemlud]

The 5min updates are not only logged by the plugin, they are real and can be seen by the dyndns provider, see attached.

07:57:53 was the time of booting the box this morning, afterwards every 5 min update attempts, which are NOT present for the ddns plugin in 22.7.last, I repeat...

[franco]

I don't think you are wrong on that end, I just meant to correct that the code tries to cache the IP, but perhaps it fails so it ends up thinking it needs to update as per interval.


Cheers,
Franco

[chemlud]

Is a bug report needed against the latest version of ddns plugin, as the problem is not present for the older version (regression)?

[franco]

Yep, thanks.


Cheers,
Franco

[chemlud]

...I have no github account, where to start?

[chemlud]

Even on latest OPNsense 23.1.3_4 the DDns is broken at least for SPdyn, as the sense is trying to refresh IP every 5 min, although no change in IP. At SPdyn the updates are logged as successful, while sense still has errors in log file:

Code Select Expand

2023-03-20T17:20:26 Notice ddclient[8506] 14361 - [meta sequenceId="4"] FAILED: was not updated because protocol <undefined> is not supported.
2023-03-20T17:20:26 Notice ddclient[8506] 13171 - [meta sequenceId="3"] FAILED: updating : unexpected status (0)
2023-03-20T17:20:26 Notice ddclient[8506] 12339 - [meta sequenceId="2"] WARNING: updating : nochg: No update required; unnecessary attempts to change to the current address are considered abusive
2023-03-20T17:20:26 Notice ddclient[8506] 11446 - [meta sequenceId="1"] FAILED: updating zhnbgr.spdns.de: unexpected status (14)


every 5 min.... epic fail.

[Patrick M. Hausen]

...I have no github account, where to start?

1. Create a github account.

[chemlud]

In my experience these bug trackers are piles of trash and another form of "write it to the wiki".

I'm not the only user observing this behaviour, why has nothing happend in the last month?

[franco]

I'm sure there are good and bad sides to GitHub. Let's take a look at a well-coordinated effort to fix recent StrongSwan regression in EAP-TLS:

https://github.com/opnsense/core/issues/6415

On the other hand, here is the ddclient maintainer on the issue that chemlud describes as "epic fail":

https://github.com/ddclient/ddclient/issues/481#issuecomment-1382166547

You need to know where to take your battles AND if you can actually win them.


Cheers,
Franco

[franco]

PS: https://github.com/ddclient/ddclient/issues/528

[chemlud]

Thanks for replying, franco, I switched the backend to OPNsense on "General Settings" and got

Code Select Expand

2023-03-21T10:07:15 Error ddclient Unable to read file /var/tmp/ddclient_opn.status
2023-03-21T10:07:05 Error ddclient Unable to read file /var/tmp/ddclient_opn.status

What's wrong here?

Is there no way to switch back ddclient to the version that worked well with 22.7.11 for the time being?

[franco]

Looks like there wasn't any value in there before. Is that still the case?

# cat /var/tmp/ddclient_opn.status

It's not impossible to revert...

# opnsense-code plugins
# cd /usr/plugins && git checkout stable/22.7
# cd dns/ddclient && make upgrade


Cheers,
Franco