Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Maurice

#1
General Discussion / Re: Internet only vlan with IPv6
November 20, 2026, 06:36:52 PM
Quote from: nero355 on November 20, 2026, 05:14:46 PMI forgot to ask : Can the 'NULL Route configuration' mentioned some time ago prevent that ?

Prevent what?

For packets handled by policy routing, a null route does nothing since the routing table is ignored.

And a null route by itself cannot prevent access from one LAN to another. It just blackholes packets to destinations which don't exist.
#2
General Discussion / Re: Internet only vlan with IPv6
November 20, 2026, 04:51:11 PM
Quote from: nero355 on November 20, 2026, 04:40:08 PMIsn't that a bit "Polluting your ISP's network" so to speak ?!

Quote from: Maurice on November 19, 2026, 06:53:16 PMA little crude, but works.

Only if a device from the IoT network actually tries to access something forbidden in one of your private networks, which shouldn't normally happen. So we're not talking about a significant amount of traffic. And it typically won't get further than the ISP's first hop. Not a big deal imho.
#3
General Discussion / Re: Internet only vlan with IPv6
November 20, 2026, 12:10:21 AM
Patrick explained how to configure it. Why / how it works: A firewall rule with a gateway directs all matching packets to this gateway, ignoring the routing table (hence "policy routing" - the firewall rule is the policy which makes the routing decision). So all packets coming from the IoT network get sent to your WAN gateway, even if their destination address is in one of your private networks. The upstream gateway then either drops them or sends them back to OPNsense, in which case they get treated like any other packet coming in on the WAN.

Cheers
Maurice
#4
Hardware and Performance / Re: OPNSense on Old Laptop
November 19, 2026, 07:06:37 PM
You can use an old laptop, but it should be old enough to still have a proper (Intel) Ethernet port. Then use VLANs and a small managed switch to split it into multiple ports as required.

I've done this before and it works fine.

Cheers
Maurice
#5
General Discussion / Re: Internet only vlan with IPv6
November 19, 2026, 06:53:16 PM
A different approach is using policy routing. Create an "allow IOT IPv6 to any" rule with the gateway set to your IPv6 WAN gateway. Then add higher priority rules without a gateway for local services / subnets you want to make accessible.

A little crude, but works.

Cheers
Maurice
#6
Thanks for the success story and the tutorial. Interesting to hear that bootefi works on this hardware and with this U-Boot build. That's not always the case...

If you use a ufs-serial-vm-aarch64 image (which defaults to a serial console), you'll have console access from the start. I create these specifically for devices without a video console.

If you erase the eMMC before you write the OPNsense image to it, you don't have to manually repair the backup GPT header.

You don't have to change anything in System / Firmware / Settings. In my aarch64 VM images, the "(default)" mirror already points to my repo.

Cheers
Maurice
#7
Official MBIM support in OPNsense would be great, but I'm not sure the umb driver in its current state would be suitable.

umb(4) was originally developed for OpenBSD in 2016 and ported to NetBSD in 2018. The NetBSD port was then ported to FreeBSD for a commercial closed source project (a plugin for OPNsense 19.7, funnily enough). This code was then open sourced in 2022, which is how it finally made it into FreeBSD 15.0.

While the original OpenBSD code is actively maintained, the FreeBSD port is essentially a snapshot from 2018. None of the improvements the OpenBSD driver received over the last 8 years - like support for additional modems and IPv6 - made it into FreeBSD.

Unless someone picks up the FreeBSD port and brings it into this decade, I'm not sure adding it to OPNsense would be worth the effort.

Just my interpretation of the status quo, not a complaint.

Cheers
Maurice


Source: About a year ago, I did a bit of testing with umb on all three BSDs, accompanied by some digging in commit histories and bug trackers.
#8
OPNsense 26.7.9 aarch64 packages and sets released. Includes hotfix 26.7.9_1.

[Update 2026-11-16]
Hotfix 26.7.9_3 released.
#9
@rdunkle84 Thanks a lot for becoming the first monthly sponsor! Much appreciated.
#10
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
#11
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
#12
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
#13
OPNsense 26.7.7 aarch64 packages and sets released.

[Update 2026-10-21]
PHP 8.5.12 released.
#14
OPNsense 26.7.6 aarch64 packages and sets released.

[Update 2026-10-10]
Hotfix 26.7.6_3 released.
#15
OPNsense 26.7.5 aarch64 packages and sets released.