OPNsense aarch64 firmware repository

[Maurice]

OPNsense 26.7.7 aarch64 packages and sets released.

[Update 2026-10-21]
PHP 8.5.12 released.

[Maurice]

OPNsense 26.7.8 aarch64 packages and sets released. Includes hotfix 26.7.8_1.

This update required respinning the build system, hence the slight delay.

[Update 2026-11-03]
Hotfix 26.7.8_2 released.


Hey everyone,

Over the 3+ years of providing OPNsense aarch64 builds, this project slowly shifted from starting as an exciting experiment to becoming somewhat of a duty. It only makes sense with frequent, timely updates. And it sometimes requires full attention on short notice, like for the PHP updates last week.

Unfortunately, as a freelancer, it becomes harder and harder to justify what is essentially an unpaid job. A decision has to be made: Pause the builds or find a way to make this a sustainable endeavour.

This is where we stand:
- The repo will continue to receive frequent updates until the 26.7 branch is end of life.
- When 27.1 gets released, the funding situation will decide whether to pause or continue.

This is what you can do:
- Become a sponsor on GitHub.
- Contact me for other sponsorship opportunities.
- If you have other funding ideas, feel free to discuss them here or contact me directly.

Cheers
Maurice

[nero355]

- If you have other funding ideas, feel free to discuss them here or contact me directly.

Why not write a nice long extensive HowTo/Tutorial and explain everyone how they can do this themselves ??

[Maurice]

The build process is the same as on amd64, which is documented in the opnsense/tools readme.
My customizations of the core package are in this single commit:
https://github.com/maurice-w/opnsense-core/commit/d49ef76
If you only build it for yourself, you don't even have to patch core. You can add the fingerprints manually instead.

But the initial setup is the (relatively) easy part. Frequently updating, building, testing and publishing everything is quite a bit of work and can't be fully automated. Having to troubleshoot build issues is not uncommon. The core team only builds it for amd64, so issues specific to aarch64 typically go unnoticed by them (understandably). And each build takes about half a day on a beefy aarch64 machine.

Everyone doing this for themselves for every single upgrade, update and hotfix would be unreasonable. The point of having a public package repo is to centralize these efforts.

There are other public OPNsense aarch64 repos, like yrzr's - my repo wouldn't exist without their pioneering work. But as far as I'm aware, mine is the only one which gets updated frequently. And I understand why, it is a real commitment.

Cheers
Maurice