Messages

Not specifically listed in the Opnsense GUI but it is supported by the plugin. Select 'custom' for the service in the GUI.

I have attached a screenshot of my OPNsense Dyndns menu.  This minimal setup creates the initial ddclient.conf file.  After enabling and saving then manually edit the config file to match content from my first message.

Happy to help.  I use https://freemyip.com.

No need to register, just to go to the website and create the name of your domain and you will receive a token (save it!).

Below is a copy of my ddclient.conf file.  Enter your token on the password line and change the last line to match the domain name that you created.


daemon=360
syslog=yes
pid=/var/run/ddclient.pid
ssl=yes
verbose=yes
use=if, if=igb0
use=web, web=freemyip.com/checkip
protocol=freemyip,
password=YOUR_TOKEN
YOURDOMAIN.freemyip.com

I performed the upgrade this morning to 22.1.9 (which included an update to the ddclient plugin).  After rebooting I found that my existing ddclient.conf file had been replaced with a newly generated version which contained the content previously entered in the OPNsense web interface.  I had manually edited my ddclient.conf file as my provider uses a token which contains an ampersand and the OPNsense web form would not allow entry of an ampersand so had I not spotted this I would have been left with a nonworking configuration.

Heads up to all who have manually customized ddclient.conf, after upgrading  check your ddclient.conf  file located in /usr/local/etc directory.  Lucky I had a copy saved elsewhere that I could transfer to the OPNsense box.

True. You have to edit the ddclient.conf file directly.

[use=cmd, cmd="/usr/local/opnsense/scripts/ddclient/checkip -i pppoe0 -t 1 -s noip-ipv4",]

I've had good luck with using the 'web' method of checking IP.  As a test, comment out the below line in your ddclient.conf file:

use=cmd, cmd="/usr/local/opnsense/scripts/ddclient/checkip -i pppoe0 -t 1 -s noip-ipv4",


and insert these:

use=if, if=igb0
use=web, web=freemyip.com/checkip


Note: igb0 is my WAN connection, if yours is different you will need to adjust.

Yes, very confusing.  Have you considered using chmod to set permissions of ddclient.conf to read only? 

This morning I upgraded to 22.1.8_1 and  rebooted afterwards.

ddclient continues to work and ddclient.conf time and date stamp remains unchanged and unaffected by rebooting.

below is the command I used to revert  (copied from the alias problem message thread)

opnsense-revert -r 22.1.7_1 opnsense

I should mention that I am running 22.1.7_1.  After upgrading to 22.1.8 I reverted because of the alias problem and as I was getting ready to leave town I didn't upgrade after the hotfix was issued because I didn't want to risk a problem.

Like you I installed the ddclient package from the GUI and once I realized that I needed to edit the config file directly I have done all subsequent work editing the file and not bothering with that section of the GUI. 

I wonder if you can revert one of your test systems to 22.1.7_1 to see whether you have uncovered an issue that is specific to 22.1.8_1?

Sorry for the delay in responding, I was out of town on vacation and didn't want to reboot my firewall remotely and risk losing access to my home network.

Back now and I just rebooted my OPNsense machine to test whether I am experiencing the same issue.

My ddclient.conf did not change as a result of a reboot and I verified that the date and timestamp on the ddclient.conf file is the same as prior to reboot.

Did you access the data using the OPNsense web interface or are you checking the file directly via ssh?  Reason I ask is that I had to edit the config file directly as my provider uses a token which contains an ampersand and the OPNsense web interface would not let me enter that value in the required field.  If I open up the web interface to review settings,  OPNsense shows me a blank field (because of the ampersand I expect) and it also does not display other values actually present in the ddclient.conf file (like the 'verbose = yes' option mentioned earlier). 

Point I am making is that on my own (working) setup, the OPNsense web interface does not show me all of the content actually in the ddclient.conf file and I am wondering if you are viewing the web interface, seeing missing content, and thinking that config file information has been overwritten.

While replying to another ddclient message thread today I reviewed my own ddclient.conf file and only then did I remember that I used the "verbose=yes" option in the config file to generate more log info.

I had to edit ddclient.conf file directly as  OPNsense web interface does not allow entry of ampersand character in some fields and my own provider uses a token which includes an ampersand.  Also the sample ddclient configuration file reveals some provider specific options in entry (protocol) which are not available from the dropdown list in the web interface.  ddclient has run flawlessly for me since I edited ddclient.conf directly using the provider specific settings.

Below is a copy of my ddclient.conf file but I have replaced my provider info with the template Namecheap info.  Tailor that to your specific circumstances, ssh into your firewall and copy the file to /usr/local/etc/ddclient.conf

 
daemon=600
syslog=yes
pid=/var/run/ddclient.pid
ssl=yes
verbose=yes
use=if, if=igb0
use=web, web=freemyip.com/checkip

## NameCheap (namecheap.com)
##
# protocol=namecheap,                     \
# server=dynamicdns.park-your-domain.com,   \
# login=example.com,                      \
# password=example.com-password           \
# subdomain.example.com

From the OPNsense menu select the log file option under the Dynamic DNS selection.  In the upper right corner from the dropdown box select 'informational' and you will see details of the ddclient update activity as shown in the below screenshot

if your IP address hasn't changed, os-ddclient will not 'update' but if you enable informational settings in the log you'll see the activity which will confirm whether it's working as intended.

Thanks for the heads up. I did the upgrade this morning and all seemed fine but after reading this post I tested my Wireguard connection (used for remote access to my home network) and it wasn't working. I use an alias for a rule specific to Wireguard VPN clients and after disabling saving and re-enabling its now working properly.