plugins os-ddclient - no independent ipv6 change detection

Important notices Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues, open and closed, and I'm convinced that mine is new.
[x] The title contains the plugin to which this issue belongs

Describe the bug Hello, I have an Internet connection where unfortunately only the IPv6 address changes and not the IPv4. When checking the IP, it seems that only the IPv4 is checked and then no change is detected. Because a set that only IPv6 should be checked unfortunately also does not work.

Expected behavior The best would be if ipv4 and ipv6 would be checked independently.

Relevant log files

2022-08-05T08:49:57	Notice	ddclient[72095]	32413 - [meta sequenceId="2"] SUCCESS: example.com: skipped: IP address was already set to 1.2.3.4.	
2022-08-05T08:49:57	Notice	ddclient[72095]	30872 - [meta sequenceId="1"] SUCCESS: *.example.com: skipped: IP address was already set to 1.2.3.4.	
2022-08-05T08:44:57	Notice	ddclient[72095]	7108 - [meta sequenceId="2"] SUCCESS: example.com: skipped: IP address was already set to 1.2.3.4.	
2022-08-05T08:44:57	Notice	ddclient[72095]	5782 - [meta sequenceId="1"] SUCCESS: *.example.com: skipped: IP address was already set to 1.2.3.4.	
2022-08-05T08:39:57	Notice	ddclient[72095]	78827 - [meta sequenceId="2"] SUCCESS: example.com: skipped: IP address was already set to 1.2.3.4.	
2022-08-05T08:39:57	Notice	ddclient[72095]	77281 - [meta sequenceId="1"] SUCCESS: *.example.com: skipped: IP address was already set to 1.2.3.4.	
2022-08-05T08:34:57	Notice	ddclient[72095]	22341 - [meta sequenceId="2"] SUCCESS: example.com: skipped: IP address was already set to 1.2.3.4.	
2022-08-05T08:34:57	Notice	ddclient[72095]	21148 - [meta sequenceId="1"] SUCCESS: *.example.com: skipped: IP address was already set to 1.2.3.4.	
2022-08-05T08:29:57	Notice	ddclient[72095]	37230 - [meta sequenceId="2"] SUCCESS: example.com: skipped: IP address was already set to 1.2.3.4.

Additional context Add any other context about the problem here.

Environment newest ddclient 1.8

Aug 05 '22 09:08 DjSni

thank you for openening this issue, I have exactly the same issue, I have a fixed IPv4 address and the IPv6 address changes, as I constantly get new IPv6 prefixes handed down from my provider.

ddclient does not send any update for the IPv6 address, since it says IPv4, nothing changed and then it happily discards IPv6 changes

Aug 05 '22 16:08 soulsymphonies

I am also a +1 but this might be a distinct issue.

I see "success" messages in the logs indicating that my IPv6 address has been sent to the dynamic DNS provider but the records on their end never change. The exact same user/password are working for IPv4.

2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 11027 - [meta sequenceId="56"] FAILED:   updating someHost.someDynamicDNSDomain.com: Invalid reply.
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 10017 - [meta sequenceId="55"] WARNING:   ERROR: Address 1.2.3.4 has not changed.
<...>
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 10017 - [meta sequenceId="43"] WARNING:  REPLIED: HTTP/1.1 200 OK
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 8427 - [meta sequenceId="42"] RECEIVE:  ERROR: Address 1.2.3.4 has not changed.
<...>
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 88939 - [meta sequenceId="31"] RECEIVE:  Server: nginx
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 87462 - [meta sequenceId="30"] RECEIVE:  HTTP/1.1 200 OK
<...>
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 85920 - [meta sequenceId="24"] SENDING:  GET /dynamic/update.php?someb64LookingHashHere HTTP/1.0
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 83846 - [meta sequenceId="23"] CONNECTED:  using SSL
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 82198 - [meta sequenceId="22"] CONNECT:  freedns.afraid.org
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 80166 - [meta sequenceId="21"] UPDATE:   updating someHost.someDynamicDNSDomain.com
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 78394 - [meta sequenceId="20"] INFO:     setting IP address to 2001:558:dead:be:eeff:d00d:aabb:ccdd for someHost.someDynamicDNSDomain.com
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 76279 - [meta sequenceId="19"] RECEIVE:  someHost.someDynamicDNSDomain.com|1.2.3.4|https://freedns.afraid.org/dynamic/update.php?someb64LookingHashHere
<...>
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 52968 - [meta sequenceId="7"] SENDING:   Connection: close
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 52968 - [meta sequenceId="6"] SENDING:   User-Agent: ddclient/3.9.1
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 52968 - [meta sequenceId="5"] SENDING:   Host: freedns.afraid.org
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 52968 - [meta sequenceId="4"] SENDING:  GET /api/?action=getdyndns&sha=b<...>d HTTP/1.0
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 50495 - [meta sequenceId="3"] CONNECTED:  using SSL
2022-08-27T18:32:48-07:00	Notice	ddclient[76079]	 44390 - [meta sequenceId="2"] CONNECT:  freedns.afraid.org
2022-08-27T18:32:48-07:00	Notice	ddclient[76079]	 40955 - [meta sequenceId="1"] WARNING:  file /var/tmp/ddclient.cache, line 3: Invalid Value for keyword 'ip' = ''

This log output comes after I disabled the "use ip6only.me" account.

Aug 28 '22 01:08 kquinsland

is there any progress here yet ?

Oct 29 '22 08:10 DjSni

This issue has been automatically timed-out (after 180 days of inactivity).

For more information about the policies for this repository, please read https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md for further details.

If someone wants to step up and work on this issue, just let us know, so we can reopen the issue and assign an owner to it.

Feb 01 '23 09:02 OPNsense-bot