gyptazy.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
To add VNET support, I'm looking for some examples of VNET jail configs, in the standard jail.conf format.
I'm particularly interested in netgraph & other less common configs, and whether the ansible-jails role should also handle deploying & configuring the epair interfaces or not.
If you have some, please gist me a URL via DM, or email dch@ the obvious email address, also works.
v2.4.0 of my ansible-jails module is now available:
https://git.sr.ht/~dch/ansible-jails
In particular, it supports base system packaged jail templates, and will use them by default on FreeBSD 15+ systems, and improved corner cases for 14.x and 16.0-CURRENT, as well.
Thanks to @beni I fixed a number of IPv6 related bugs, and no-IP jails bugs too.
It has a significant improvement in test coverage thanks to Ansible Molecule, and https://sourcehut.org/ CI, so we know that both post-jail templates & ZFS usage works as expected!
v3.0.0 might come out this week, with VNET jail support. I don't expect this to be a significant change, it's just that I personally never tested it, and it seems like a good milestone.
This morning after reading the #FreeBSD Handbook chapter on Jails I had a massive realization. Look, I've dabbled in jails over the years but it was really just scratching the surface. But after reading about VNET Jails....this is some deep, mind-expanding awesomeness. One can run entire workloads completely segregated by a complex virtual network with VLAN tagging, independent network stacks, routing, and switching internally on one OS on a single kernel. Not that I have a use for it (yet) but this is truly exponentially mind blowing.
It's clear FreeBSD is *the* infrastructure operating system.
#BSD #RunBSD #tech #homelab #vnet #Jails #FreeBSDJails #infrastructure #networking