os-ddclient Multi-WAN scenario, all get the same public IP

[Deutschi]

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

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

Describe the bug
I have multiple WAN interfaces, each one is connected to a modem - so every WAN interface in OPNsense gets a LAN IP. Until now, I used the legacy dyndns client to update multiple No-IP domains, one for each WAN interface. The new os-ddclient works as expected if there is only one entry made - the public IP of the interface is correctly determined. However, once I enable the second entry for the second WAN interface, os-ddclient finds one IP and sets this one for every entry.

To Reproduce
Steps to reproduce the behavior:

1. Go to Dynamic DNS settings of the new os-ddclient
2. Add an entry for a specific WAN interface, save and apply (works)
3. Add another entry for a different interface, same Provider, different domains/hostnames, save and apply
4. All entries get the same IP address

Expected behavior
Every entry should be considered independent and get a different public IP address.

Screenshots
Legacy Dyndns (working):

"new" os-ddclient:

Additional context

• I have no special settings in my outgoing NAT, just the automatic stuff.
• This is not a visual bug, the single IP gets submitted to No-IP for all domains.

Environment
OPNsense 22.1.10_4-amd64
FreeBSD 13.0-STABLE
OpenSSL 1.1.1q 5 Jul 2022

Plugin: os-ddclient 1.8

[Links2004]

Having a very similar problem but with IPv4 + IPv6 updates.
os-ddclient does always use the IPv4 interface address, which is bad.

the legacy dyndns is working perfectly fine, for my use case.

Versions

OPNsense: 22.7.9-amd64
FreeBSD :13.1-RELEASE-p5
OpenSSL: 1.1.1s 1 Nov 2022

[OPNsense-bot]

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.