Messages

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

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

Sorry for the long silence everyone. While the project is still very much alive within Mono, the cooperation between them and me is paused indefinitely.

In the meantime, please direct all questions directly to Mono.

Cheers
Maurice

OPNsense 26.7.7 aarch64 packages and sets released.

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

OPNsense 26.7.6 aarch64 packages and sets released.

[Update 2026-10-10]
Hotfix 26.7.6_3 released.

OPNsense 26.7.5 aarch64 packages and sets released.

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

[Update 2026-09-17]
unbound 1.26.1 released.

Könnte schon der axp-Treiber sein bzw. dessen Interaktion mit PPPoE + VLAN-Tagging.

Hast Du die Möglichkeit, das Glasfasermodem 2 an den SFP-Ports zu testen, und / oder die GPON-SFPs an den Intel-Ports (mittels Kupfer-SFP / Medienkonverter / Switch )?

Eventuell ein Problem in der Konstellation FreeBSD / axp-Treiber / PPPoE? Ist aber Spekulation.

Ausschließen würde ich, dass es am PMG3000-D20B liegt. Das verwende ich auch und bekomme beim Ookla-Speedtest auch im Single Connection-Modus die volle Geschwindigkeit, ebenso in der Praxis z. B. bei einzelnen Downloads mit fetch oder wget.

Allerdings ist mein Konstellation deutlich anders. Das GPON-SFP sitzt in einem MikroTik-Router, der auch die PPPoE-Verbindung aufbaut. OPNsense (VM) sitzt dahinter als Firewall. Die Faser ist ebenfalls von der Telekom, ISP ist jedoch Telefonica / o2.

Grüße
Maurice

OPNsense 26.7.3 aarch64 packages and sets released. Includes hotfix 26.7.3_8.

[Update 2026-09-04]
Hotfix 26.7.3_11 released.

Statistics update: Average monthly traffic is now at ~165 GB.

Btw, a positive side effect of this is reduced resource consumption since unbound doesn't have to load the respip module anymore. I noticed a considerably lower RAM usage baseline.

Cheers
Maurice

OPNsense 26.7.2 aarch64 packages and sets released. Includes base / kernel 26.7.2_4, core 26.7.2_2 and hostapd 2.12_2.

If you don't want OPNsense itself to use NAT64, then you need to configure a DNS server without DNS64 in System / Settings/ General.

Did you enable DNS64? Then it's expected behavior. IPv6 is generally preferred over IPv4 and it doesn't matter whether the destination address is a "native" IPv6 address or an address synthesized by DNS64.

Cheers
Maurice

Privacy Extensions (RFC 4941) und Stable Privacy (RFC 7217) sind unterschiedliche Mechanismen.

Privacy Extensions spielen hier in der Tat keine Rolle, da diese nur zusätzliche Adressen für Outbound-Verbindungen erzeugen.

Stable Privacy ändert hingegen den Interface Identifier selbst, wenn sich das Präfix ändert. Das betrifft dann auch Inbound-Verbindungen und ist inkompatibel zu dieser DynDNS-Methode.

Ob Stable Privacy verwendet wird musst Du auf dem Wordpress-Server nachschauen (und dort auch ggfs. deaktivieren). OPNsense hat darauf keinen Einfluss.