Recent posts

#1

Development and Code Review / Re: UniFi Gateway emulator

Last post by amd989 - Today at 04:21:13 AM

Why do you want the USG in your UniFi Controller while all USG models are declared EOL officially and should be avoided since about 1 year ago ?!

The point of this app is to emulate a USG device backed by OPNSense, there is no real USG whether its EOL or not is not the point.

In other words, it is just a shim/facade. UniFi thinks OPNSense it's a USG, that's all. Now you can see OPNSense stats inside UniFi Controller. Something you couldn't before.

But you bring a valid point. I guess you could technically emulate the latest device, in the inform protocol, it is just a string identifier. I would just need to find out what that string is and maybe we could unlock more features within UniFi's controller.

I hope this clarifies it.

#2

26.1 Series / Re: Kea DHCPv4 fails to start ...

Last post by fengchen_opn - Today at 03:57:47 AM

I read a bit through the KEA mailing list and this looks related:

https://lists.isc.org/pipermail/kea-users/2026-March/006027.html

Yes, I do see this log:
DHCP4 failed to open service sockets — the maximum number of attempts (0) was exhausted without success.

#3

26.1 Series / Re: Kea DHCPv4 fails to start ...

Last post by fengchen_opn - Today at 03:52:56 AM

After upgrading to OPNsense 26.1.6

Are you from the future ?

;)


/Could not resist... ^_^

😂

#4

26.1 Series / Re: Stuck on 26.1.2_5 unable t...

Last post by hakuna - Today at 03:33:47 AM

SOLVED.

There are quite a lot of posts with folks having similar problem when trying to update from X to Y
Somebody had the same problem as me going from 25.7.11_9 to 26.1.1 posted 2 months ago on Reddit.
The solution was to run via terminal: opnsense-bootstrap

I finally got 26.1.5 update installed.
Plugins were removed like the UPnP, other set as missing and I had to reinstall them like ISC DHCP which is running.

I have no idea what happened when 26.1.2_5 was installed but this seems to be a normal thing here and there.

#5

26.1 Series / Re: Stuck on 26.1.2_5 unable t...

Last post by hakuna - Today at 03:05:06 AM

I tried changing the repo location via GUI again and this is what I get but OPNSense seems unable to download it.

Code Select Expand

***GOT REQUEST TO UPDATE***
Currently running OPNsense 26.1.2_5 (amd64) at Wed Apr  1 11:58:42 AEDT 2026
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (2 candidates): .. done
Processing candidates (2 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking integrity... done (0 conflicting)
Nothing to do.
Checking all packages: ......... done
Nothing to do.
Nothing to do.
Starting web GUI...done.
Installation out of date. The update to opnsense-26.1.5 is required.
***DONE***


#6

26.1 Series / Re: Stuck on 26.1.2_5 unable t...

Last post by hakuna - Today at 03:01:13 AM

I checked the repo config which I never ever touch, and it looks correct to me.
Via GUI is set as default/default/Community since always.

Code Select Expand

root@firewall01:~ # cat /etc/pkg/FreeBSD.conf
#
# To disable this repository, instead of modifying or removing this file,
# create a /usr/local/etc/pkg/repos/FreeBSD.conf file:
#
#   mkdir -p /usr/local/etc/pkg/repos
#   echo "FreeBSD: { enabled: no }" > /usr/local/etc/pkg/repos/FreeBSD.conf
#

FreeBSD: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/quarterly",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}
FreeBSD-kmods: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/kmods_quarterly_${VERSION_MINOR}",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}



#7

26.1 Series / Re: Stuck on 26.1.2_5 unable t...

Last post by hakuna - Today at 02:56:54 AM

Check your repository configuration, if you added more than the standard OPNsense repository that might be your issue.

If you added more repos (which always is a manual shell operation) you should know where to look in the filesystem.

Thank you for the reply but that is the problem, I have made no changes at all.

Out of the blue, I have the plugins:

* os-apcupsd (missing)
* os-isc-dhcp (missing)
* os-nut (missing)

They are red in colour and have an "+" instead of the delete icon, but they are installed.

I swear, I have made no changes so idk what to do or change to fix this.
I tried changing the repo location via the GUI last night as my last hope but that didn't work.

The only major change was to install 26.1.5_2 update.
I checked for update, read the release note, and applied, I do not touch repo config.

#8

26.1 Series / New features

Last post by sopex8260 - Today at 12:43:56 AM

What are some neat features you would like to see on opnsense?

#9

26.1 Series / Re: DHCP Stopped Tagging Lease...

Last post by mtowagb - Today at 12:11:40 AM

I suspect this is happening due to a configuration file on a partition that is not deleted by the OS installation process, but I have to figure out which one that is exactly.

#10

Zenarmor (Sensei) / Re: Zenarmor performance @ Int...

Last post by OPNenthu - March 31, 2026, 11:57:40 PM

Podman is just an alternative to Docker and something I don't feel like maintaining either :)

That's the beauty of it: you don't manage anything.  It manages itself, including updates.  You don't touch a thing on the OS.  From the user perspective it's just an app installer.  You run it.  It installs UOS.  Done.

That wasn't the case in the past.  You needed to install and maintain Docker yourself, as well as each container (MongoDB, Network) and their connections.

It's the same crap like with Docker : https://github.com/containers/podman/blob/main/docs/tutorials/basic_networking.md

I don't need those additional Network Interfaces on my Host ;)

There are none.  It doesn't change anything on your host network and what you'll see in 'ip a' is the same as what you had before.  It listens on the host IP rather than some internal 172.x address like what Docker does with virtual interfaces.

This is all I see on my UOS VM:

Code Select Expand

$ ip -4 a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: ens18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    altname enp0s18
    altname enxbc2411e2f30a
    inet 192.168.1.116/24 brd 192.168.1.255 scope global dynamic noprefixroute ens18
       valid_lft 73385sec preferred_lft 58071se

Just add the host IP to DNS as 'unifi.' and you're done.  Maybe also open the needed host firewall ports.

The entire UOS stack is hidden from you in its own podman context.  You don't interact with it.  Just install it in a VM and see.

Maybe this from ChatGPT explains it best:

UniFi OS isn't just "Podman + containers"—it's a full appliance OS. It uses its own management layer to:

• deploy containers
• restart them
• control networking
• enforce updates

So even though Podman is underneath, you're not meant to interact with it directly like a normal host.