[Solved] ddclient, dyndns protocol <undefined> is not supported

[tracerrx]

Using ddclient and dyndns, my logs are full of

Code Select Expand

FAILED: was not updated because protocol <undefined> is not supported.

The fix appears to be adding curl=yes to the config file as documented here: https://forums.gentoo.org/viewtopic-t-1157764.html?sid=68e7996f3c1d84fa9568be5d94fb83b9

Anyone else seeing or try this? 

[tracerrx]

This just began happening somewhere in the 23.1.x series... Was working fine before that...

[tracerrx]

Legacy appears to work just fine... however is this still true?

Code Select Expand

Please make sure to upgrade to os-ddclient before 23.7 is released as this plugin will be removed from our repository

[chemlud]

...deadly true. and no discussion/debat possible apparently.

I asked for an amount of money to be raised, to fix this once and for ever. I never got a reply

https://forum.opnsense.org/index.php?topic=32355.msg160640#msg160640

[tracerrx]

I truly understand @franco frustration with the devs running these projects and lack of willingness to keep their projects up-to-date.  If we could find a stable and active client that supports the multitude of services out there, I'm sure he would be willing to do the work to get it integrated.

Hopefully @mimugmail will move the legacy plugin into his repo for now so that those of us who need a working dyndns solution have one.

[franco]

Did you try 23.1.9's update? https://github.com/opnsense/plugins/commit/ff873cc2f1659

But it needs a restart of ddclient which the update doesn't do if there is no reboot to cause it.


Cheers,
Franco

[tracerrx]

I had just installed 23.1.9 and noticed I was still having the issue.  I did not restart the service before I moved over to the legacy client however.  Will give it a quick try and report back shortly.

[tracerrx]

Nope.. still fails:

Code Select Expand


2023-05-31T11:18:27-04:00 Notice ddclient[32622] 37956 - [meta sequenceId="7"] WARNING: Wait at least 5 minutes between update attempts.
2023-05-31T11:18:27-04:00 Notice ddclient[32622] 37956 - [meta sequenceId="6"] WARNING: last updated <never> but last attempt on Wed May 31 11:18:23 2023 failed.
2023-05-31T11:18:27-04:00 Notice ddclient[32622] 37956 - [meta sequenceId="5"] WARNING: skipping update of XXXXXXXXX.homeip.net from <nothing> to 1XX.XXX.XXX.XXX.
2023-05-31T11:18:23-04:00 Notice ddclient[6866] 23450 - [meta sequenceId="4"] FAILED: was not updated because protocol <undefined> is not supported.
2023-05-31T11:18:23-04:00 Notice ddclient[6866] 20074 - [meta sequenceId="3"] FAILED: updating : unexpected status (0)
2023-05-31T11:18:23-04:00 Notice ddclient[6866] 17246 - [meta sequenceId="2"] WARNING: updating : nochg: No update required; unnecessary attempts to change to the current address are considered abusive
2023-05-31T11:18:23-04:00 Notice ddclient[6866] 14493 - [meta sequenceId="1"] FAILED: updating saraniti-boniello.homeip.net: unexpected status (12)

[franco]

Can you check the ddclient config? Might also be wrong still.

# grep ifv4 /usr/local/etc/ddclient.conf

Should yield at least one result if properly applied.


Cheers,
Franco

[franco]

PS: Which provider is that? This seems related: https://github.com/ddclient/ddclient/issues/481

[tracerrx]

When service is stopped its empty.  When service is running:

Code Select Expand

root@OPN-Boniello:~ # grep ifv4 /usr/local/etc/ddclient.conf
usev4=ifv4, ifv4=igb0, \

Provider is DynDNS

[franco]

Thanks that should be dyndns2 and we may be missing this fix https://github.com/ddclient/ddclient/commit/fa6c95f5110

I can build a test version tomorrow

EDIT: Or today... https://github.com/opnsense/ports/commit/9318efdf3d1 build coming soon.


Cheers,
Franco

[tracerrx]

It is DynDNS2! Will take a look at the patch and see if I can apply without you doing a release...

[franco]

Snapshot test version:

# opnsense-revert -z ddclient-devel

To get back to "stable" one:

# opnsense-revert ddclient-devel

Make sure to restart again. I'm not sure if patches work cleanly but I'm positive you can try and help me.

Side note: there is a commit about version 3.11.0 in the works... https://github.com/ddclient/ddclient/commit/d3a353990

And let's please not complain about lack of effort :)


Thanks,
Franco

[chemlud]

Franco, no one ever complained about unmotivated admins in this project iirc. :-)

But the frustration with dyndns nearly let the dev team abandon this functionality completely, if I got your comments over the last months/years correct. So: Nice to see that apparently even with 23.7 onwards there will be some kind of dyndns functionality in OPNsense... ;-)