Seamless login/logout with ZFS Encrypted Home Directories

RE: https://ipv6.social/@litchralee_v6/115801351770788902

I've not forgotten about my adventures into a #FreeBSD home router. It's merely been on pause lol.

But I plan to restart soon, now that I also have a print copy of @pitrh 's The Book of PF, 4th Edition.

Wait what the hell happened, #FreeBSD allows AI contributions?

Damn. This changes everything :-(

My #FreeBSD #HomeLab adventures continue. With some basic shell scripts and mtree I've added a rudimentary intrusion detection system. Do others do something similar, is there a much better solution I should be aware of?

https://henryleach.com/2026/03/basic-intrusion-detection-system-with-mtree/

#BSD #RunBSD

Basic Intrusion Detection System with mtree

After the very basic server setup, having some kind of simple Intrusion Detection System (IDS) seems like a good idea. While all the previous steps were designed to prevent someone taking control of your server, if someone has managed to tamper with something, short of being locked out - how would you know?

Notes
Here I am spending 4h of my personal FTE over a Saturday lunchtime, on qualifying an aftermarket Dell VEP 1400 white box edge router from a Scottish IT recycler for #FreeBSD use. It has 6x1000BASE-T and USB 3 for 5G/4G radio. #OPNsense 26.2 serial boots just fine, but does not support the RJ45 ports or the #Qualcomm #ath10k Wi-Fi. The two #SFP ports seem to work just fine with #Cisco compat 1000BASE-T SFP modules. These are not combos (shared), I am pleased to report so far.

Just spent way too long wrestling with a 400-line pf.conf and asymmetrical routing. 😵‍💫

The culprit? Classic rule ordering. A slightly too broad rule (with quick) near the top was happily catching traffic and creating states without the reply-to option before my intended rule could even look at it.

The packets were flowing, just... not back the right way. Debugging that was significantly harder than I expected.

I am officially logging off to take a nap. 💤

#pf #PacketFilter #Networking #Sysadmin #FreeBSD #OpenBSD

What's the fuss about FreeBSD? Read about my first impressions here, after playing with it these past three months on my servers (and, since a few weeks, on my laptop):

https://kedara.eu/playing-freebsd/

My special thanks to the awesome and kind #BSDCafe Barista @stefano for writing the posts that introduced me to the BSDs, and for fostering such a positive and welcoming community!

#FreeBSD #RunBSD #ZFS #BlogPost

@Chris1776 @clf

Yes. Release Highlights for 580.142 comments about it.
https://www.nvidia.com/en-us/drivers/details/265444/

If you need legacy 580 series (currently at 580.142) for old GPUs on #FreeBSD you can use:
x11/nvidia-kmod-580
x11/nvidia-driver-580

And if you prefer DRM/KMS interface, one of
graphics/nvidia-drm-{510|515|61|66|latest}-kmod-580
that matches your base FreeBSD version is needed additionally.

If you need #NVIDIA #Linux libraries, you additionally need:
x11/linux-nvidia-libs-580

Note that, as "-devel" variants of NVIDIA #GPU drivers on FreeBSD #ports tracks whichever newer one of New Feature Branch (NFB) or Production Branch (PB), "-devel" variants are currently at 595.58.03, too. Both 580.142 and 595.58.03 are released this month (Mar., 2026).

Beta drivers are just triggers for us to start investigating for upcoming NFB or PB, thus, FreeBSD ports should never been bumped for them (although supports for testing could appear earlier with upgrades for PB, NFB or legacy drivers).

And one of the related thread in forums.freebsd.org here.
https://forums.freebsd.org/threads/urgent-nvidia-rel15-0-580-119-02_1-of-nvidia-driver-drm61-kmod-are-known-broken.101377/

Driver Details | NVIDIA

Download the <dd~LanguageName> <dd~Name> for <dd~OSName> systems. Released <dd~ReleaseDateTime>

NVIDIA
Defining the Social Media Applications

Define a custom app on both Mastodon and Twitter for automated posting with Python. Set up credentials for your script, then call the API.

Bob's Pages of Travel, Linux, Cybersecurity, and More