plugins: dns/ddclient: no-ip broken
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 IP address changes to WAN interface are not detected and sent to No-IP service, and ddclient logs the following messages:
ddclient[43123] 60634 - [meta sequenceId="2"] WARNING: unable to determine IP address
ddclient[43123] 59557 - [meta sequenceId="1"] WARNING: found neither ipv4 nor ipv6 address
Doesn’t matter what combination of Check ip method and Interface to monitor I use:
Check ip method: Interface, Interface to monitor: WAN Check ip method: noip-ipv4, Interface to monitor: WAN Check ip method: noip-ipv4, Interface to monitor: none
I prefer the Interface/WAN method as this keeps detection local and only sends data to no-ip when there are changes.
The generated ddclient.conf is:
daemon=300
syslog=yes # log update msgs to syslog
pid=/var/run/ddclient.pid # record PID in file.
verbose=yes
ssl=yes
use=if, if=vtnet1, \
protocol=noip, \
login=xxxx, \
password=yyyy \
my.no-ip-name.net
I started using ddclient late last year, and this has “always” been an issue for me.
To Reproduce Steps to reproduce the behavior:
- Add a Noip service
- Choose Check IP method = Interface
- Choose Interface to monitor = WAN
As mentioned I have also tried using Check IP method = noip-ipv4, same result.
Expected behavior The public IP is correctly detected, change sent to No-IP service if update is needed.
Relevant log files
ddclient[43123] 60634 - [meta sequenceId="2"] WARNING: unable to determine IP address
ddclient[43123] 59557 - [meta sequenceId="1"] WARNING: found neither ipv4 nor ipv6 address
Workaround Modifying the ddclient.conf as follows:
From:
use=if, if=vtnet1, \
To:
use=if, if=vtnet1
And restarting the service - but this only persists until next reboot or update.
Environment OPNsense 22.1.9 (amd64, OpenSSL) Proxmox VM Host CPU pass-through: Intel® Core™ i3-8109U CPU @ 3.00GHz (2 cores, 2 threads) Network: VirtIO
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 5
- Comments: 19 (8 by maintainers)
I was able to successfully update IPs for no-ip hostnames by configuring the service type ‘custom’.
@maxkratz, nicely done, thank you. Your workaround solved my issue as well - now my ddclient can detect the WAN IP address and update if needed.
Worked for me!! Thanks
I don’t think this is a technical problem we can solve by fiddling with a timeout. 10 seconds is more than enough for a healthy connection.