Using ddclient and dyndns, my logs are full of 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?
This just began happening somewhere in the 23.1.x series... Was working fine before that...
Legacy appears to work just fine... however is this still true?
Please make sure to upgrade to os-ddclient before 23.7 is released as this plugin will be removed from our repository
...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
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.
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
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.
Nope.. still fails:
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)
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
PS: Which provider is that? This seems related: https://github.com/ddclient/ddclient/issues/481
When service is stopped its empty. When service is running:
root@OPN-Boniello:~ # grep ifv4 /usr/local/etc/ddclient.conf
usev4=ifv4, ifv4=igb0, \
Provider is DynDNS
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
It is DynDNS2! Will take a look at the patch and see if I can apply without you doing a release...
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
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... ;-)
Applied patch, cleared log, restarted service and I still get the below:
2023-05-31T13:13:39-04:00 Notice ddclient[31901] 36422 - [meta sequenceId="7"] WARNING: Wait at least 5 minutes between update attempts.
2023-05-31T13:13:39-04:00 Notice ddclient[31901] 36422 - [meta sequenceId="6"] WARNING: last updated <never> but last attempt on Wed May 31 13:13:31 2023 failed.
2023-05-31T13:13:39-04:00 Notice ddclient[31901] 36422 - [meta sequenceId="5"] WARNING: skipping update of XXXXXXXXXX.homeip.net from <nothing> to 1XX.XXX.XXX.XXX.
2023-05-31T13:13:31-04:00 Notice ddclient[6081] 20843 - [meta sequenceId="4"] FAILED: was not updated because protocol <undefined> is not supported.
2023-05-31T13:13:31-04:00 Notice ddclient[6081] 18500 - [meta sequenceId="3"] FAILED: updating : unexpected status (0)
2023-05-31T13:13:31-04:00 Notice ddclient[6081] 16680 - [meta sequenceId="2"] WARNING: updating : nochg: No update required; unnecessary attempts to change to the current address are considered abusive
2023-05-31T13:13:31-04:00 Notice ddclient[6081] 14514 - [meta sequenceId="1"] FAILED: updating XXXXXXXXXX.homeip.net: unexpected status (12)
@franco sent you a PM with complete output of /usr/local/etc/ddclient.conf and created a test domain for you to use
I debugged this just now (yay, it's Perl!) and this is the bad line inside nic_dyndns2_update():
https://github.com/ddclient/ddclient/blob/841ffcbdaa009687e5fb390c4527055e929f959a/ddclient.in#L4197
Replace with:
my $h = $hosts[0];
In all honesty I don't understand how it tries to handle multiple host names here by browsing through the result line by line (one hostname one line????).
Cheers,
Franco
PS: https://github.com/ddclient/ddclient/pull/542
Here we go!
https://github.com/ddclient/ddclient/commit/1c91a5aa84
https://github.com/opnsense/ports/commit/87bbf9d6d9
# opnsense-revert -z ddclient-devel
Should install ddclient-devel-3.10.0_3...
Cheers,
Franco
Looks good! Thanks for the fix!
2023-06-01T09:43:27-04:00 Notice ddclient[45849] 75262 - [meta sequenceId="9"] FAILED: updating XXXXXX.homeip.net: unexpected status (0)
2023-06-01T09:43:27-04:00 Notice ddclient[45849] 73342 - [meta sequenceId="8"] SUCCESS: updating XXXXXX.homeip.net: good: IPv4 address set to 100.XXX.XXX.XXX
2023-06-01T09:43:27-04:00 Notice ddclient[45849] 72011 - [meta sequenceId="7"] FAILED: updating XXXXXXXX.homeip.net: unexpected status (12)
2023-06-01T09:43:21-04:00 Notice ddclient[26837] 32556 - [meta sequenceId="6"] WARNING: Wait at least 5 minutes between update attempts.
2023-06-01T09:43:21-04:00 Notice ddclient[26837] 32556 - [meta sequenceId="5"] WARNING: last updated Thu Jun 1 09:42:32 2023 but last attempt on Thu Jun 1 09:42:32 2023 failed.
2023-06-01T09:43:21-04:00 Notice ddclient[26837] 32556 - [meta sequenceId="4"] WARNING: skipping update of XXXXXXX.homeip.net from 1XX.XXX.XXX.XXX to 100.XXX.XXX.XXX.
2023-06-01T09:42:33-04:00 Notice ddclient[55964] 68145 - [meta sequenceId="3"] FAILED: updating XXXXXXXX.homeip.net: unexpected status (0)
2023-06-01T09:42:33-04:00 Notice ddclient[55964] 65768 - [meta sequenceId="2"] WARNING: updating XXXXXXXX.homeip.net: nochg: No update required; unnecessary attempts to change to the current address are considered abusive
2023-06-01T09:42:33-04:00 Notice ddclient[55964] 63951 - [meta sequenceId="1"] FAILED: updating XXXXXXXX.homeip.net: unexpected status (12)
Works!
But still doesn't show Current IP or time updated in GUI.
Is it suppose to do this?
I'm not sure about the GUI, but it does show up in the status file:
/var/tmp/ddclient.cache
But that's only for dyndns2. I think duckdns and other code paths are still broken upstream.
Cheers,
Franco