os-ddclient

[tracerrx]

I hate to add to this thread... However it appears that ddclient does not work in multi wan environments.  I use DynDNS, and when I set dd-client to Interface to monitor (None) and Check IP Method (Interface):

Code: [Select]

2022-03-18T13:38:37-04:00 Notice ddclient[320] 54434 - [meta sequenceId="5"] WARNING: found neither ipv4 nor ipv6 address
2022-03-18T13:38:33-04:00 Notice ddclient[97610] 53819 - [meta sequenceId="4"] WARNING: found neither ipv4 nor ipv6 address
2022-03-18T13:38:07-04:00 Notice ddclient[55511] 54044 - [meta sequenceId="3"] WARNING: found neither ipv4 nor ipv6 address
2022-03-18T13:38:05-04:00 Notice ddclient[50294] 53561 - [meta sequenceId="2"] WARNING: found neither ipv4 nor ipv6 address
2022-03-18T13:37:21-04:00 Notice ddclient[36503] 28394 - [meta sequenceId="1"] WARNING: found neither ipv4 nor ipv6 address
2022-03-18T13:08:27-04:00 Notice ddclient[84274] 92874 - [meta sequenceId="1"] WARNING: found neither ipv4 nor ipv6 address
2022-03-18T12:58:27-04:00 Notice ddclient[84274] 13239 - [meta sequenceId="1"] WARNING: found neither ipv4 nor ipv6 address
2022-03-17T21:18:24-04:00 Notice ddclient[84274] 95262 - [meta sequenceId="1"] WARNING: file /usr/local/etc/ddclient.conf: file /usr/local/etc/ddclient.conf must be accessible only by its owner (fixed).
2022-03-17T20:48:24-04:00 Notice ddclient[84274] 77262 - [meta sequenceId="1"] WARNING: found neither ipv4 nor ipv6 address
Only by setting the interface to monitor as a single wan does it appear to work.  Any way to make it always report just the current default wan ip in multi-wan environments?

[Hansaplastique]

Not sure if I should report this here or not, but os-ddclient doesn't seem to support the cPanel web call either.
(cPanel documentation)

Short version:
In cPanel you enable the DDNS feature for a domain or subdomain.
cPanel will then generate a unique URL when setting this up, something like this:

https://mydomain.com/cpanelwebcall/somecharactershere

When calling this link, no username, password, or other complicated things are needed.
Just submit the link. cPanel will update the appropriate records and returns a plain text reply, formatted like so:

Code: [Select]

ipv4: 123.123.123.123
(where 123.123.123.123 is obviously your public IP address)

The old DDNS in OPNSense handled this just fine by selecting "Custom", however "os-ddclient" (v1.3) doesn't work that way ...
Anyhoo - hope this is useful for the involved developer or developers - apologies if this is not the right place to report this. 😊

For reference, a similar request for pfSense (not by me).

[CGrisamore]

Adding this to the thread to help out other users of freemyip.com and to inform the developers of the current issue that requires workaround with this dynamic DDS provider.

freemyip.com doesn't require a username and password.  At the time your custom domain is created you are provided a token which is used to refresh your ip address when properly accessed.  freemyip.com supports ddclient and they provide a configuration (below) where you populate the username and password fields with your custom token

# Configuration for freemyip.com
custom=yes
server=freemyip.com
protocol=dyndns2
login=YOUR_TOKEN
password=YOUR_TOKEN
YOUR_DOMAIN.freemyip.com

Currently you cannot populate these values through the Opnsense web interface as the token includes an ampersand character and Opnsense restricts entry of an ampersand in the username field (see below)



You must edit the ddclient.conf file directly to enter your token in the two fields after which it works fine.

[Sopor]

I can't get the os-ddclient 1.3 to work with FreeDNS. After adding token to password field (as in the old plugin) it will disappear even if i save it. I have even tried adding it to user name. Here it will be saved but it will still not work.

I can't use ( or ) in the description field either. It will show this error message:
Description should be a string between 1 and 255 characters

Will there be a widget for this plugin too?

[mrpink]

With username and password (no token) FreeDNS is working here.

[dennyo]

Same Problem here, I have IONOS and I need to ask an Update URL which works fine with os-dyndns but no Chance with os-ddclient.

No Host, no Username, no Password, just Update URL containing pubkey/api-token and for ex. var for pushing IPv6 oder IPv4.
Please get it to work else ddclient won't be an alternative to dyndns!

Not sure if I should report this here or not, but os-ddclient doesn't seem to support the cPanel web call either.
(cPanel documentation)

Short version:
In cPanel you enable the DDNS feature for a domain or subdomain.
cPanel will then generate a unique URL when setting this up, something like this:

https://mydomain.com/cpanelwebcall/somecharactershere

When calling this link, no username, password, or other complicated things are needed.
Just submit the link. cPanel will update the appropriate records and returns a plain text reply, formatted like so:

Code: [Select]

ipv4: 123.123.123.123
(where 123.123.123.123 is obviously your public IP address)

The old DDNS in OPNSense handled this just fine by selecting "Custom", however "os-ddclient" (v1.3) doesn't work that way ...
Anyhoo - hope this is useful for the involved developer or developers - apologies if this is not the right place to report this. 😊

For reference, a similar request for pfSense (not by me).

[Sopor]

It seems that we are back to use User name and password on FreeDNS. So, now it is working 

Update: I was wrong... It is not working

FAILED: Could not get freedns update URLs from freedns.afraid.org

WARNING: file /usr/local/etc/ddclient.conf: file /usr/local/etc/ddclient.conf must be accessible only by its owner (fixed).

WARNING: file /var/tmp/ddclient.cache, line 3: Invalid Value for keyword 'ip' = ''

I hope you will fix all the bugs before you remove the legacy version ...

[jeekee]

Hi guys,

Having the same problems. DDclient won't work for me if set to monitor interface WAN or if set to noip-ipv4 or 6 nor if set to dyndns. It does however work if set to freedns.

Nice add on would be if we could see the retrieved ip address the same as with the legacy ddns client.

KR JeeKee

[wmeter]

Does not work. I'm with DynDNS, and the old plugin worked fine. The new plugin has no indication whatsoever if it ran successfully or not, and the logs remain empty in my setup. Checking the update logs on the DynDNS side show zero activity from the new plugin... I'm 'reachable' by the grace if the last dynamic DNS update from the old plugin and the fact that my 4G did not reboot yet.... Same multi-wan setup here... Going to revert back to the old plugin until ddclient runs reliable...

[tracerrx]

@wmeter same here but im continuing to use it... waiting to see if I ever get an update in the dyndns logs.. As you said nothing to indicate its working in local logs.  Also I cant get it to even start if set to default (none) interface in multi-wan.

[thefunkygibbon]

I hate to add to this thread... However it appears that ddclient does not work in multi wan environments.  I use DynDNS, and when I set dd-client to Interface to monitor (None) and Check IP Method (Interface):

Code: [Select]

2022-03-18T13:38:37-04:00 Notice ddclient[320] 54434 - [meta sequenceId="5"] WARNING: found neither ipv4 nor ipv6 address
2022-03-18T13:38:33-04:00 Notice ddclient[97610] 53819 - [meta sequenceId="4"] WARNING: found neither ipv4 nor ipv6 address
2022-03-18T13:38:07-04:00 Notice ddclient[55511] 54044 - [meta sequenceId="3"] WARNING: found neither ipv4 nor ipv6 address
2022-03-18T13:38:05-04:00 Notice ddclient[50294] 53561 - [meta sequenceId="2"] WARNING: found neither ipv4 nor ipv6 address
2022-03-18T13:37:21-04:00 Notice ddclient[36503] 28394 - [meta sequenceId="1"] WARNING: found neither ipv4 nor ipv6 address
2022-03-18T13:08:27-04:00 Notice ddclient[84274] 92874 - [meta sequenceId="1"] WARNING: found neither ipv4 nor ipv6 address
2022-03-18T12:58:27-04:00 Notice ddclient[84274] 13239 - [meta sequenceId="1"] WARNING: found neither ipv4 nor ipv6 address
2022-03-17T21:18:24-04:00 Notice ddclient[84274] 95262 - [meta sequenceId="1"] WARNING: file /usr/local/etc/ddclient.conf: file /usr/local/etc/ddclient.conf must be accessible only by its owner (fixed).
2022-03-17T20:48:24-04:00 Notice ddclient[84274] 77262 - [meta sequenceId="1"] WARNING: found neither ipv4 nor ipv6 address
Only by setting the interface to monitor as a single wan does it appear to work.  Any way to make it always report just the current default wan ip in multi-wan environments?

I'm getting these in my logs when i'm just set to WAN and it has a normal IPv4 address.

Also, I notice that there is an option to 'check' every x amount of seconds for an address change (default 300) but is there a way of forcing the update to the dyndns provider on a set schedule anyway?  as some providers (like noip who i use) require you to update every x amount of days else they disable the account.  obviously if my ip hasnt changed in a couple of months, then it won't auto update the provider. (if i understand it correctly)

:edit: just installed the old dyndns client and it works fine.
please don't deprecate the old client?  at least not until the new one is actually fit for purpose!

[AhnHEL]

@franco

Will os-ddclient eventually be listed as a Service in SYSTEM: DIAGNOSTICS: SERVICES so it can conveniently be stopped or restarted from the Dashboard Widget?

Code: [Select]

Edit:  Request was added in ddclient 1.5 on 4/7/2022 with update 22.1.5.

[nicesense]

I have the problem that the new os-ddclient (1.4) is not working by using WAN failover:

I tried to use the recommended new os-ddclient plugin with my WAN-Failover-Gateway-Group setting. But there is no choice to select WAN-Failover-Interface on the setting "Interface to monitor" during configuration. You can choose "Interface to monitor" = none , but this has no effect. The host will not be updated.

In contrast to it, the legacy os-dyndns plugin had supported this option.

Has somebody similar problems? Is there a solution (planed)?

[hescominsoon]

IIRC ddclient is supposed to be the version opnsense is switching to?  i tired it and I get constant cnanot  determine external IP address errors.  the "legacy" dyndns client works fine for me at no-ip.

[tracerrx]

I reverted back to dyndns client, everything works as expected in multi-wan environment (with a dynDNS host).