That guide is for non-vnet jails. If you want vnet, use this one:<p><a href="https://blog.uidrafter.com/engineering/freebsd-jails-network-setup" rel="nofollow">https://blog.uidrafter.com/engineering/freebsd-jails-network...</a><p>Why VNET?
"VNET jails give each jail its own isolated copy of the network stack"
<a href="https://klarasystems.com/articles/virtualize-your-network-on-freebsd-with-vnet/" rel="nofollow">https://klarasystems.com/articles/virtualize-your-network-on...</a>
I found jails kind of accidentally. A few years back I built a NAS at home and wanted to run ZFS on it, so FreeBSD was an obvious choice. I soon found out how easy it is to create and manage jails: you just start a new one from a template, get an ip address, ssh into it and `pkg install` whatever you need. I now run over 10 jails, having home automation, media player, grafana, few different databases, unifi controller and so on all in their own jails.<p>I like the simplicity and how straightforward it is to add new servers to our home. I have long history with docker, but kind of prefer the way of being able to ssh into the jail and manage it like a normal server distro. Docker again is much nicer in the daily development flow, where I want nine different databases in a clean state every morning.
<a href="https://bastillebsd.org" rel="nofollow">https://bastillebsd.org</a> is a great tool if you want to deploy tiny container-like Jails on FreeBSD. I've been using it in production for a while and it's been a great tool.
Jails are nice but it has always seemed like a system where you don’t need another copy of userland would be better (eg sandboxing). It’s wasteful and you might forget to apply security patches.