Messages

I have setup the build system according to the documents available.  As Maurice says, "But the initial setup is the (relatively) easy part. "

With each new release there is real work to make the system build each time.  I am very thankful that Maurice has the public repo.  He has made maintaining an arm64 Opnsense system a reality.   If the public repo disappears I will probably be forced back to pfsense.

I suggest people hit the sponsor button on Maurice's github page.  I do not want to go back to pfsense.

I have realtek nics on two systems.
I am using arm64.
I compile the ports myself or fetch the package and manually install the driver.

realtek is supported by these ports:

https://www.freshports.org/net/realtek-re-kmod/
https://www.freshports.org/net/realtek-rge-kmod/

This is the one for arm64:
https://www.freshports.org/net/realtek-re-kmod198/

To bootstrap the process you could use a usb nic to get connectivity.

I had major problems with Unifi U-6 Lite and Pixel 6 and 6a devices. No problems with other wifi devices.  The first thing to check is the version of Unifi software.  Some of the Unfi versions simply did not work with Pixel devices.  I am currently at 10.3.58.  Earlier solution, I also found that I had to set the ipaddress and NOT use dhcp on the Pixel.  I do not know if that is still the case.  The problems went away with updates to Unifi and Android version  updates (currently version 16).  Connections were worthless until the slow progression of updates from Android and Unifi.

That is it exactly:
https://github.com/opnsense/core/issues/9135

I switched to Kea and using dhcpv6.  I noticed that Android 16 devices started to work with and use ipv6.  I found that each device was requesting a dedicated prefix.  Appears strange and wasteful.   I looked into this and found an article:
android-developers.googleblog.com/2025/09/simplifying-advanced-networking-with.html

I am using OPNsense 25.7.4 and PFSense. The OPNsense has some sort of issue with the dhcpv6, prefix delegation, and routing.  I think the routes are not being created for prefix delegation.  I found that PFsense appears to work with the dhcpv6, and prefix delegation without a problem.

24.7.2
Clean install not upgrade.
I see an error on console:
HTTPS: Could not open file or uri for loading certificate from /var/etc/cert.pem
00206149AD9D0000:error:16000069:STORE routines:ossl_store_get0_loader_int:unregistered scheme:/usr/src/crypto/openssl/crypto/store/store_register.c:237:scheme=file
00206149AD9D0000:error:80000002:system library:file_open:No such file or directory:/usr/src/crypto/openssl/providers/implementations/storemgmt/file_store.c:267:calling stat(/var/etc/cert.pem)
Unable to load certificate

OPNsense 24.1 aarch64 ....  is working well on Orange Pi 5 Plus.

Would you mind sharing your build or the steps you took? I'm trying to get it working on my OPI5+ as well. Thank you.

The first step is to change the firmware of the OPI5+ to use EDK2 firmware.
https://github.com/edk2-porting/edk2-rk3588
If you do that then you can use the OPNsense images.

I noticed that when creating the cloudflare api token, Acme required:
Zone Resources set: Include | All zones.   This appears to be the problem.
To sum it up:
Zone | DNS | Edit
Zone Resources | Include | All Zones
Client IP (not using this field)
TTL | set a valid date range
This appears to work OK.

OPNsense 24.1 aarch64 ....  is working well on Orange Pi 5 Plus.

Update to 24.1 r1 went fine.  Everything seems to be working normally.

This is really good work!  I am now running on orange pi 5 plus.  There were no problems at all.