Recent posts

#1
General Discussion / Re: Internet only vlan with IP...
Last post by Maurice - Today at 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
#2
I did not want to update prematurely, but I do not believe I've had a single unexplained failure since replacing the RAM, so thank you for pointing me in that direction! I will see if I can update this to show Solved.
#3
Tutorials and FAQs / Re: OPNsense aarch64 firmware ...
Last post by Maurice - Today at 05:58:50 PM
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
#4
26.7, 26.10 Series / Re: https://nginx2root.com/ Is...
Last post by franco - Today at 05:49:45 PM
os-caddy is the best default replacement, os-haproxy covers advanced proxying, and os-OPNWAF covers application-layer security (for business users). Together, they make os-nginx largely redundant on OPNsense, also because the plugin itself is in a mostly unmaintained state as opposed to the other three.


Cheers,
Franco
#5
Did you create additional source nat rules for the second wireguard tunnel? I tried once I think to do it as a 'group' but connections were flaky until I separated it all out.
#6
26.7, 26.10 Series / Re: https://nginx2root.com/ Is...
Last post by Timeraider - Today at 05:14:51 PM
Quote from: franco on <strong>Today</strong> at 05:11:06 PMWe will be providing an update through a snapshot build tomorrow, but it requires to do a full ports build which takes 10 hours so we can publish it tomorrow.

It's not a hotfix priority so 26.7.10 will pick it up next week.


Cheers,
Franco

Not blaming or judging anything .. just curious, but do you by any chance know why its not really a hotfix priority.
Based on the requirements and way of exploiting, it sounds like it could be decently dangerous for the nginx plugin so wondering whats the reasoning.. is it simply not that easy to exploit in the current way the nginx plugin is set up, is it due to turning off http/2 being an easy workaround or is there a different reason?
#7
26.7, 26.10 Series / Re: https://nginx2root.com/ Is...
Last post by franco - Today at 05:11:06 PM
We will be providing an update through a snapshot build tomorrow, but it requires to do a full ports build which takes 10 hours so we can publish it tomorrow.

It's not a hotfix priority so 26.7.10 will pick it up next week.


Cheers,
Franco
#8
26.7, 26.10 Series / Re: [CALL FOR TESTING] DHCP re...
Last post by franco - Today at 05:07:13 PM
@chucksense sounds like the perfect test setup for both calls :)

Incidentally, another ancient issue was raised regarding the ping use in the TIMEOUT handling, which probably isn't worth asking for general feedback, but since this call is open I'll leave it here for additional testing on top of the other commit:

# opnsense-patch https://github.com/opnsense/core/commit/08125db80b


Cheers,
Franco
#9
Adding to Cedrik: ZFS is also way more resilient to frequent power failures than UFS, so even in case of a single boot device, use ZFS.
#10
26.7, 26.10 Series / Re: Speed drops?
Last post by RouterGuy2019 - Today at 04:38:51 PM