Recent posts

#1

26.1 Series / Re: Management: Status: Firmwa...

Last post by nancy266 - Today at 05:22:58 AM

Problem solved...

in Addition to OpenVPN there was Wireguard configured, but with disabled peer (Instance was left enabled).

After disableing the Instance too escape road 2, Firmwarecheck via Management started working again.

Strange behaviour in my opinion...

#2

Hardware and Performance / Re: [Work In Progress] OPNsens...

Last post by BrandyWine - Today at 01:48:32 AM

Hello,
Which version i could try to install on my Radxa E52C?
It have an RK3582 chip, ty.

Well, no free lunch.
Just build it.
Here's a guide, but you will perhaps not build on your RK device.
https://yrzr.github.io/tutorial-build-opnsense-arm64-on-a-rpi4/

#3

26.1 Series / Re: lots of empty space in new...

Last post by tessus - Today at 12:27:34 AM

It seems that even though Tabulator was updated and the grid height is auto calculated in the 26.1.6 update, the problem still persists (without
Stylus or Tampermonkey).

Excerpt from the release notes:

ui: upgrade Tabulator to version 6.4.0
ui: automatic grid height calculation

#4

26.1 Series / Re: 26.1.6 - Health Check

Last post by (MARLOO) - Today at 12:06:01 AM

Updated to 26.1.6 from previous 26.1.5 ; upgrade initially hung in GUI but completed cleanly via CLI (pkg update -f, pkg upgrade, opnsense-update, reboot).

Unbound + dnscrypt-proxy stack fully operational post-upgrade (correct listeners, dig tests OK, dnscrypt query logs PASS).

Firewall/NAT, IPv6 (track6), and WebGUI all behaving as expected so far.

System hostwatch is running correctly after the update and "Automatic Discovery" is enabled on the desired interfaces.
Please double‑check under Interfaces → Neighbors → Discovery that "Automatic Discovery" is ticked and that the correct interfaces are selected, then apply the changes.

Thanks

#5

26.1 Series / Re: 26.1.6 - Health Check

Last post by ProximusAl - April 09, 2026, 11:56:19 PM

I have zero idea what the heck happened.

How old was the OPNsense installation ?

Sounds like ZFS issues that sometimes happen when the FreeBSD Bootloader is too old...

4 months...Device was new in December 25 and fresh installed with 25.7 then.

#6

26.1 Series / Re: New features

Last post by xpendable - April 09, 2026, 11:20:37 PM

You phrase it in such a way that it appears to not be usable but you can already use it manually without much effort.

It was also reworked in FreeBSD 15 and that's the reason we're halting further efforts to present it in the GUI until we're on 26.7 and things have stabilised.


Cheers,
Franco

Sorry I was under the impression you still needed to rebuild the kernel, I guess that's not the case since FreeBSD 14. So I went ahead and enabled it with the sysctl tunables and I'll see how it goes.

#7

26.1 Series / Re: OpenVPN - VPN Not Working ...

Last post by Patrick M. Hausen - April 09, 2026, 11:15:56 PM

@haim9080 if you want any help, you need to be way more specific. WireGuard is generally easier to set up for a site to site VPN or a single (or a handful of) road warrior(s). It offers a modern design, relies on PKI only, good performance. It does not offer centralised management, user authentication via external sources (LDAP, Active Directory, ...) etc.

What exactly did you do when you "tried and failed"? What do you want to achieve in the first place? Are you managing both the OPNsense firewall and the client endpoints?

#8

26.1 Series / Re: 26.1.6 - Health Check

Last post by nero355 - April 09, 2026, 11:08:08 PM

I have zero idea what the heck happened.

How old was the OPNsense installation ?

Sounds like ZFS issues that sometimes happen when the FreeBSD Bootloader is too old...

#9

26.1 Series / Re: OpenVPN - VPN Not Working ...

Last post by nero355 - April 09, 2026, 10:58:48 PM

So what the solution about that case ??

Not using any VPN stuff on any kind of device these days, sorry! :)

#10

26.1 Series / Kea DDNS in practice...

Last post by Ed V. - April 09, 2026, 10:04:33 PM

I feel like I missed something very basic here...

Is there a way to specify a manual config file should be used versus the default template?

The various options for DHCP-DDNS (tsig-keys, ddns-domains, etc.) are overwritten with the default empty values whenever I start the Agent, and I can't seem to find where that overlay is hiding in the system.

The current OpnSense docs say to put the settings in the DHCP4 or DHCP6 files, but the DDNS variables are not recognized by those daemons.

I have a valid DDNS config (or at least the command line validation says it's all good), but the overwrite is driving me even more batty than usual.

Help?