Open perryflynn opened 5 days ago
When possible, please open a pull-request. currently the nsupdate
action seems to be backgrounded, if you make it blocking, it might stall the boot process. (with a pull-request
we can review and offer feedback)
PR is opened.
@AdSchellevis ddclient also supports nsupdate. But as it looks like that protocol is not yet exposed to the OPNSense UI. Does it maybe make sense to replace the rfc2136 plugin with os-ddclient?
@perryflynn it might be worth a try if that works better, but my advise would be to first install ddclient (without our plugin package) and test it out. If it works as expected, just let me know what it needs so we can discuss how to implement it there.
Important notices Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
Similar to #2752, updating my DynDNS Domain via the rfc2136 plugin does not work. I added some log lines to the plugin code and it looks like the update fails at
rc.bootup
because the internet connection is not established yet. Later onrc.newwanip
the plugin reports the IP was not changed and the nsupdate call is skipped.To Reproduce
Expected behavior
The plugin should not create a cache file when the nsupdate fails and should retry the nsupdate when the router is finally online.
Relevant log files
Additional context
My workaround is to delete the cache files when the exit code of the nsupdate command is not zero.
My change in
/usr/local/etc/inc/plugins.inc.d/rfc2136.inc
:Environment Software version used and hardware type if relevant. e.g.:
OPNsense 24.1.9_4-amd64 FreeBSD 13.2-RELEASE-p11 OpenSSL 3.0.14
Manufacturer: PC Engines Product Name: apu4