Messages

16

22.1 Legacy Series / Re: os-ddclient

« on: June 12, 2022, 03:54:07 pm »

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

opnsense-revert -r 22.1.7_1 opnsense

17

22.1 Legacy Series / Re: os-ddclient

« on: June 12, 2022, 03:45:10 pm »

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?

18

22.1 Legacy Series / Re: os-ddclient

« on: June 12, 2022, 03:17:55 pm »

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.

19

22.1 Legacy Series / Re: os-ddclient

« on: June 07, 2022, 02:23:16 pm »

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.

20

22.1 Legacy Series / Re: ddclient invalid reply talking to Namecheap

« on: June 07, 2022, 01:38:33 pm »

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

21

22.1 Legacy Series / Re: os-ddclient

« on: June 06, 2022, 04:33:23 pm »

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

22

22.1 Legacy Series / Re: How to force a ddclient update?

« on: May 31, 2022, 04:49:00 pm »

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.

23

22.1 Legacy Series / Re: Alias based firewall rules doesn't work after upgrade to 22.1.8

« on: May 25, 2022, 07:28:14 pm »

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.

24

22.1 Legacy Series / Re: os-ddclient

« on: March 20, 2022, 01:51:27 pm »

Adding this to the thread to help out other users of freemyip.com and to inform the developers of the current issue that requires workaround with this dynamic DDS provider.

freemyip.com doesn't require a username and password.  At the time your custom domain is created you are provided a token which is used to refresh your ip address when properly accessed.  freemyip.com supports ddclient and they provide a configuration (below) where you populate the username and password fields with your custom token

# Configuration for freemyip.com
custom=yes
server=freemyip.com
protocol=dyndns2
login=YOUR_TOKEN
password=YOUR_TOKEN
YOUR_DOMAIN.freemyip.com

Currently you cannot populate these values through the Opnsense web interface as the token includes an ampersand character and Opnsense restricts entry of an ampersand in the username field (see below)



You must edit the ddclient.conf file directly to enter your token in the two fields after which it works fine.