os-ddclient

[Vesalius]

I guess we will need to @franco to expound then. My take is that "you can always use this and take it anywhere..."

Code: [Select]

# pkg create os-dyndns
Creating package for os-dyndns-1.27_2
# ls
os-dyndns-1.27_2.txz

[skyeci2018]

I am using no ip on a test machine. Whilst my script file seems to work for the initial contact with no ip I dont see any further entries in the log file for when it polls for updates/checks?

How can I see if its polling every 5 minutes or how do you make it update every 5 minutes?

thanks

[TrueType]

I agree there is no way to see if the connection is working. I want the feature "Cached IP" as can be shown in the DynDNS-plugin. Much easier to see if it's working..

I tried to install ddclient 2 times before and first time it was not working for me since cloudflare was not an option, then it was added so I tried again but then I could not see if it was working but I hoped it did since I  followed the instruction.
But then suddenly my Dynamic IP changed and when I was away and needed to connect to my server, poof, the ddclient had not updated as it should...

[CGrisamore]

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

[skyeci2018]

Thanks very much for your help . I will try this out.

[CGrisamore]

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.

[skyeci2018]

Thanks for your tip - I added the verbose entry and I can see another entry after 5 minutes so it appears to be working.

I do have one problem though - every time I reboot the machine the ddclient.conf reverts to the default file - why is it not saving the info after reboot?



thanks

[skyeci2018]

Can anyone help with this please?
I do have one problem  - every time I reboot the machine the ddclient.conf reverts to the default so my config is lost...

Thanks

[CGrisamore]

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.

[skyeci2018]

Hi

Yes I am editing the file directly over ssh. I have 2 test units here and as soon as I reboot either of them the config I added to the .conf file is lost....no reboot all seems to work fine... the timestamp reverts back to the original file date etc
Both test units are running the latest versions of opnsense etc.

am at a loss with this issue.. someone else mentioned it further up the thread but that didn't get a response either.

I installed the package from the gui so I am not sure if this is the cause of the issue. How do you install the package manually?

cheers

[CGrisamore]

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?

[skyeci2018]

Happy to try if someone can offer the command line

my current test box is on OPNsense 22.1.8_1
for my own sanity I tried the process from scratch again but the outcome is the same.

cheers

[CGrisamore]

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

opnsense-revert -r 22.1.7_1 opnsense

[skyeci2018]

thanks I tried it but it failed - I might just rebuild it as the same version as yours and see if the issue is there or not. Its only a test box so I will do that

[CGrisamore]

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.