Awesome news for #opensource #networking professionals and fans:
#Protectli now offers Vaults with #OpenWrt pre‑installed!
This is exactly why open‑source firmware matters. Long‑term updates, transparent security fixes, no forced obsolescence, and full control over your device.
Proprietary routers age out fast.
OpenWrt‑based devices stay useful for years.
https://protectli.com/news/openwrt-preinstalled-on-protectli-vaults/
Idea: Something like the #HeltecV4, but in m.2 form. it would expose a serial interface with which the host OS can communicate. Bonus points for separate rx and tx antennas.
This would enable us to deliver the whole solution in a single enclosure (a #Protectli appliance).
Watching jakkuh my dream home datacenter YouTube video…
So many really nice things he is talking about…. But how am I buying TWO Unifi Enterprise Fortress Gateways… $2k each.
My router is #OPNsense on a used #Protectli FW4B.. 150 EUR
@bacardi55 I use #Protectli with #OPNsense but for home and <1GB ISP connections, consider the cheap Velocloud, <USD $40
This morning I finally replaced the home router. The new one is a Protectli V1211. I imported my OPNsense configuration, then updated to the latest release. If you're reading this post, it's working.
The whole thing was remarkably painless. The only tricky part was that I had to reassign all the interfaces and VLANs to match the new box's hardware.
The old router is on hot standby until the new one has soaked for a few days.
Thanks all for the feedback.
===
UPDATE: Protectli suspects that it's a race condition in igc(4). According to them OpenBSD's igc might not be as stable as the driver for Linux.
===
I received a brand new Protectli VP2430 yesterday and it felt very solid. I've installed OpenBSD 7.7 stable and have been testing it by running ssh vp2430 'cat /dev/random' >/dev/null the whole night and most of today. First from one host it reached 72 MByte/sec with a load of 1.6. Then added another ssh session and it topped at 118 MByte/sec with a load of 3.8. It got quite hot but I could still hold my hand on it without burning.
This was all over igc0, then I started testing on igc1 with a MTU of 1420 (but the VPN server was another host) and after about 4 hours I got a kernel panic. I'm not sure if it has anything to do with igc(4):
Fabián Rodríguez 🛡💾 🇨🇴 🌴
Sudo Sudo Sudo ⒶⒺⓋ
Shawn Webb
Stefan 
treefifty
Kernel Bob 
kuijsten*cpu2: vmmaplk rwlock 0xfffffd8401c63698: enter read deadlock
ddb{2}> trace
db_enter() at db_enter+0x14
panic(ffffffff82553cb9) at panic+0xdd
rw_do_enter_read(fffffd8401c63698,0) at rw_do_enter_read+0x175
uvmfault_lookup(ffff800048a9f3b0,0) at uvmfault_lookup+0x8a
uvm_fault_check(ffff800048a9f3b0,ffff800048a9f3e8,ffff800048a9f418,0) at uvm_fault_check+0x38
uvm_fault(fffffd8401c635b0,6cc016ed000,0,1) at uvm_fault+0xed
kpageflttrap(ffff800048a9f530,6cc016ed024) at kpageflttrap+0x158
kerntrap(ffff800048a9f530) at kerntrap+0xaf
alltraps_kern_meltdown() at alltraps_kern_meltdown+0x7b
uvm_map_uaddr(6cc016ed000,6cc016ed000) at uvm_map_uaddr+0x1e
uvm_map_splitentry(fffffd8401c635b0,6cc016ed000,6cc016ee000,0) at uvm_map_splitentry+0x20b
sys_mprotect(ffff800048a847f0,ffff800048a9f7d0,ffff800048a9f740) at sys_mprotect+0x17c
syscall(ffff800048a9f7d0) at syscall+0x5ec
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x701102e59f30, count: -14
$ pkg_info
intel-firmware-20250512v0 microcode update binaries for Intel CPUs
inteldrm-firmware-20250509 firmware binary images for inteldrm(4) driver
quirks-7.103 exceptions to pkg_add rules
symon-2.89p0 active host monitoring tool
updatedb-0p0 pkg_add speed up cache
vmm-firmware-1.16.3p0 firmware binary images for vmm(4) driver