Messages

Happy belated New Year - and Happy Friday on top!  Firstly, congrats on 26.1 !  Looking good . . .

Question about upgrading from OPNsense 25.7.11_9-amd64 - I have a virtual instance running under Proxmox - quite smoothly I might add for some time.  Took me a while to configure multiple VLANs, Zenarmor, Unbound, Netbird and ISC DHCP that everything works, but once all set up - has been very stable (even after multiple upgrades over the last 16 months)

I'm a bit nervous about the ISC DHCP changeover to DNSMasq - not just because of many static leases (saw Network Guy article which I've tested on a test instance - worked well)

My question is, for a relatively small HomeLab environment - Should I just upgrade to 26.1 and keep ISC DHCP as a plugin??  Any downsides to keeping ISC moving forward?

If I do choose to change to DNSMasq, should I do it BEFORE or AFTER the 26.1 upgrade ?!?

The old saying of "Don't touch a running system" always comes to mind in this scenario :-)

Thanks in advance and once again, Congrats on the new release!

Quick update - for kicks, I changed to development branch - did the Update - then installed netbird plugin - the changed back to community branch and netbird development plugin stays installed ;-)  Strange way to test a single plugin, but better than nothing . . .

Understood - Thx.  Any timeline when it goes into stable community?

Go to Firmware and change from Community to Development.

Install all updates.

Afterwards go to plugins and you can find a os-netbird-devel if you check the show community plugins checkbox.

Thanks! But that means I need to run development tree - so there is no way to just install that one plugin under community release??

I'd like to get netbird running on my 25.7 box - but the plugin is not in the community repo - after some research, I found it here: https://github.com/opnsense/plugins/tree/master but not sure how to get it installed ?!?

Any tips would be welcome!

what happens with the ISC DHCP services

Nothing, really. ISC DHCP4 is still part of 25.7.

Understood - so even though DNSMasq DHCP is standard in 25.7 when using the setup wizard, if you import an older 25.1 backup file which had ISC it will then activate ISC just like before . . . no conflict with DNSMaq . . .

Quick question - if I have 4 different VLANs and ISC DHCP currently configured and working in 25.1 - save a backup of the config - then install a fresh instance of 25.7 and import the 25.1 config - what happens with the ISC DHCP services ?? Do they get automatically translated into DNSMasq DHCP ? Or should the backup be imported without DHCP and manually configure DNSMasq?

Thx in advance!

If I manually start the ddclient from the console, seems to work fine:  ddclient -daemon=0 -debug -verbose -noquiet

Under general settings I have the interval set to default 300 seconds - but there are no automatic updates being performed - nothing in the logs except the manual updates ?!?

The native backend doesn't use ddclient.conf nor ddclient itself. Look at /usr/local/etc/ddclient.json instead.

I know it's confusing. Maybe one day we will even remove the ddclient backend or split the plugins into two.


Cheers,
Franco

Gotcha !  So when I choose "native" backend - it clears out the ddclient.conf - and doesn't work.

When I change backend back to ddclient - it seems to keep my ddclient.conf after hitting apply. Only thing is, I don't see it updating automatically (respecting the 300 second default interval) . . . shouldn't I see an update attempt every 5 minutes in the ddclient logs ??

 

That is to be expected since each apply will generate the complete configuration file with the information found in the config.xml.

Huh? Maybe I'm not explaining this correctly.  If I use the GUI under Dynamic DNS to create a DynDNS account configuration using native backend - and save it using apply, it doesn't work.  When I look at the resulting ddclient.conf I see only:

root@FoxOPN:/usr/local/etc # cat ddclient.conf
syslog=yes                  # log update msgs to syslog
pid=/var/run/ddclient.pid   # record PID in file.

Which doesn't show the items I placed in the GUI under accounts like login, password, ssl, etc.

Is the ddclient.conf being generated on the fly together with the config.xml settings?  I don't get it . . .

> when using the GUI, it resets the manually made ddclient.conf and doesn't respect the settings made ?!?

That's intentional.  You could always use ddclient without the plugin, but then also without a widget and other hooks into the system.

The middle ground is get your missing features into the plugin.


Cheers,
Franco

Thx Franco - I know it's intentional that the ddclient.conf file is overwritten from the GUI plugin - but don't think it's intentional that the GUI does not respect the settings made and NOT put them into the ddclient.conf - I have one entry under accounts - filled out correctly, but when I hit apply, it saves and overwrites the ddclient.conf file with only those two entries found above ?!?  So hitting apply breaks the config . . .

Patch works great! But I noticed that when configured through the GUI - it doesn't work (using DynDNS) - have to configure the /usr/local/etc/ddclient.conf by hand - when using the GUI, it resets the manually made ddclient.conf and doesn't respect the settings made ?!?

Manually created - which works fine:
root@FoxOPN:/usr/local/etc # cat ddclient.conf
daemon=300
syslog=yes                  # log update msgs to syslog
pid=/var/run/ddclient.pid   # record PID in file.
ssl=yes

usev4=ifv4, ifv4=vtnet1, \
protocol=dyndns2, \
login=(redacted), \
password=(redacted)\
xxxx.homeip.net

After hitting "apply" in the GUI:

root@FoxOPN:/usr/local/etc # cat ddclient.conf
syslog=yes                  # log update msgs to syslog
pid=/var/run/ddclient.pid   # record PID in file.

Got it - Thx - will try in a test environment before I muck up my production environment . . .

Out of curiosity, what are the defaults in a "fresh" install of OPNSense 25.7 ?? Is unbound and dnsmasq automagically used ??

Wow - on the surface, dnsmasq seems complex - like setting DHCP reservations, changing default GW or DNS conflict with Unbound is not so intuitive like the ISC DHCP
Always keen to learn something new - but these are many confusing options available ?!?

A simple guide or how-to convert from ISC to dnsmasq (also considering unbound) might be helpful - or if you can point me in the right direction?

Thx

Understood - I have a small network with like 100 clients divided into 4 VLANs - so I guess I will look into Dnsmasq - no rush to change . . .

Thanks for your prompt reply!