ddclient-devel is broken

Started by almodovaris, January 22, 2023, 08:05:53 PM

Previous topic - Next topic
January 22, 2023, 08:05:53 PM Last Edit: January 22, 2023, 08:10:10 PM by almodovaris
It says:


Use of uninitialized value $h in hash element at /usr/local/sbin/ddclient line 4                                                                                                                                                                                                                                             105.
Use of uninitialized value $h in hash element at /usr/local/sbin/ddclient line 4                                                                                                                                                                                                                                             107.
Use of uninitialized value $h in hash element at /usr/local/sbin/ddclient line 4                                                                                                                                                                                                                                             108.
Use of uninitialized value $_[0] in sprintf at /usr/local/sbin/ddclient line 216                                                                                                                                                                                                                                             3.
SUCCESS:  updating : good: IP address set to xx.xx.xxx.xx
Use of uninitialized value $h in hash element at /usr/local/sbin/ddclient line 4                                                                                                                                                                                                                                             105.
Use of uninitialized value $_[0] in sprintf at /usr/local/sbin/ddclient line 216                                                                                                                                                                                                                                             3.
FAILED:   updating : unexpected status (0)
Use of uninitialized value in string ne at /usr/local/sbin/ddclient line 1157.
Use of uninitialized value in string ne at /usr/local/sbin/ddclient line 1157.
Use of uninitialized value in string ne at /usr/local/sbin/ddclient line 1157.
Use of uninitialized value in string ne at /usr/local/sbin/ddclient line 1157.
Use of uninitialized value in string ne at /usr/local/sbin/ddclient line 1157.
Use of uninitialized value in string ne at /usr/local/sbin/ddclient line 1157.
Use of uninitialized value in string ne at /usr/local/sbin/ddclient line 1157.
Use of uninitialized value in string ne at /usr/local/sbin/ddclient line 1157.
Use of uninitialized value in string ne at /usr/local/sbin/ddclient line 1157.
Use of uninitialized value in string ne at /usr/local/sbin/ddclient line 1157.
Use of uninitialized value in string ne at /usr/local/sbin/ddclient line 1157.
Use of uninitialized value in string ne at /usr/local/sbin/ddclient line 1157.
Use of uninitialized value in string ne at /usr/local/sbin/ddclient line 1157.
Use of uninitialized value in string ne at /usr/local/sbin/ddclient line 1157.
Use of uninitialized value in string ne at /usr/local/sbin/ddclient line 1157.
Use of uninitialized value in string ne at /usr/local/sbin/ddclient line 1157.
Use of uninitialized value in string ne at /usr/local/sbin/ddclient line 1157.
Use of uninitialized value in string ne at /usr/local/sbin/ddclient line 1157.
FAILED:    was not updated because protocol <undefined> is not supported.


Reverting to stable ddclient (ddclient-3.9.1.pkg) solves the problem (but you should backup the folder /usr/local/opnsense/scripts/ddclient beforehand and then restore it).
OPNsense HW:

Minisforum Venus series UN100C, 16 GB RAM, 512 GB SSD
T-bao N9N Pro, 16 GB RAM, 512 GB SSD

Please report it to upstream. We're not having any more complaints either way: https://github.com/ddclient/ddclient


Cheers,
Franco

Hello devteam,

do you still want to switch to the program, despite the very poor supports?
If someone has several firewalls with ddclient active and his dnydns-provider changes method to update IP he will be unable to use it until the ddclient-master will update it, seen, that i added regfish.de early october an until now it has not been released a new release with service integrated i think ddclient can not be the solution for such a important service.
I know it its possible to use custom but if the service does not work after a while you have to access a lot of firewalls to move from configured service to custom but this can not be a solution.

Greeting

One thing I want to avoid is discuss upstream issues here in the forum. We are not at liberty to impose quality requirements on third party software that was actively being asked for by community in the past either indirectly or directly. Just be careful what you wish for. ;)


Cheers,
Franco

Hi Franco, maybe you can elaborate a little on the state of OPNsense internal discussion on the future of dynamic DNS with 23.7 and beyound?
kind regards
chemlud
____
"The price of reliability is the pursuit of the utmost simplicity."
C.A.R. Hoare

felix eichhorns premium katzenfutter mit der extraportion energie

A router is not a switch - A router is not a switch - A router is not a switch - A rou....

This incremental change was released today:

https://github.com/opnsense/plugins/blob/94d04f74c8481ea58a09aa707bde6245c9a1ef49/dns/ddclient/pkg-descr#L9-L14

We will keep doing these as requests and contributions come in. os-dyndns is scheduled for final removal in 23.7.


Cheers,
Franco

As soon as I change the backend to OPNSense the ddclient service does not start any longer, even without ANY config. Can anyone confirm?

Edit: running OPNSense 23.1.6

Yes, because it doesn't use ddclient. There might be a problem with the PID file lookup. I'll try to fix.


Cheers,
Franco


How can I patch it into my system?

Thanks!

# opnsense-patch -c plugins f920b48a94
# service configd restart


Cheers,
Franco

Patching worked as well as the Cloudflare DNS updates now (dual stack).

Thanks, franco!

Ok prefect, thanks for testing! 8)

Hi,

can anybody explain the "OPNsense backend"?

I was using ddclient and the backend was selected to ddclient.
My domain was updated, however ddclient could not understand the response code from the provider, so I also never saw the IP in the OPNsense GUI. Also ddclient always retried to set the IP, although it was already set.

I now changed the backend to "OPNsense".
I see now, that the ddclient service is not running anymore.
However, in the Dynamic DNS settings, I now see my IP and the time of the latest update.
Also in the log-file I see a notice "execute" for my account every 10min.
I have to verify it with a change of the IP, but for now it seems to work.

What I do not really understand:
What happens if I change the backend to "OPNsense"?
Is this an alternative to os-ddclient and os-dyndns?
Or is this a part of ddclient?

I am especially curious, as my ddclient service now is not running anymore.

It's a rewrite to leverage the "ddclient" frontend handling without actually having to use the ddclient software on the backend.


Cheers,
Franco