New 𝗔𝗿𝗲 𝗙𝗿𝗲𝗲𝗕𝗦𝗗 𝗝𝗮𝗶𝗹𝘀 𝗮 𝗖𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿𝘀? (Are FreeBSD Jails a Containers?) on the blog.
https://vermaden.wordpress.com/2025/04/08/are-freebsd-jails-containers/
New 𝗔𝗿𝗲 𝗙𝗿𝗲𝗲𝗕𝗦𝗗 𝗝𝗮𝗶𝗹𝘀 𝗮 𝗖𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿𝘀? (Are FreeBSD Jails a Containers?) on the blog.
https://vermaden.wordpress.com/2025/04/08/are-freebsd-jails-containers/
Publique en mi blog un tutorial de como actualizar las Jails de FreeBSD con Bastille.
Bastille es una herramienta para manejar jaulas en FreeBSD de manera facil y organizada.
#FreeBSD #BastilleBSD #tutorial #iagostoblog #websencilla
https://blog.iagosto.dev/entradas/actualizar-jails-con-bastille-en-freebsd
New video out
Using Templates with #bastilleBSD on #FreeBSD (#Jails)
Enjoy
On #youtube
https://youtu.be/t1nhPU43Bng
On #Odysee
https://odysee.com/@YetanotherSysAdmin:0/Using-Templates-in-Bastille-on-FreeBSD:1
New video out
Using Templates with #bastilleBSD on #FreeBSD (#Jails)
Enjoy
On #youtube
https://youtu.be/t1nhPU43Bng
On #Odysee
https://odysee.com/@YetanotherSysAdmin:0/Using-Templates-in-Bastille-on-FreeBSD:1
Toc-toc #freebsd guys ! I created a bridge0 and Vnet running tailscale into #bastillebsd jail. Bridge and Vnet are connected using epair. I read on forum that rules from #pf operate on epair and not bridge, so I need to skip bridge0 in #pf rules ? Bridge0 is 193.168.42.1 connected with re0. Another thing, I want to separate/isolate my local network (192.168.1.0) from jails vnet network 192.168.42.0/24. Actually when I ping a local network address like 193.168.1.80 from the tailscale jail with epair 192.168.42.2, ping works... Isolation between networks don't work by default, and I search the good pf rules to isolate 192.168.42.0 from local network ... Any help appreciated.
New video out
Creating a #nginx #jail on #FreeBSD leveraging #bastilleBSD
Enjoy
On #youtube
https://youtu.be/K_6OOLcghjg
On #Odysee
https://odysee.com/@YetanotherSysAdmin:0/Using-Bastille-to-create-Jails-on-FreeBSD:2
New video out
Creating a #nginx #jail on #FreeBSD leveraging #bastilleBSD
Enjoy
On #youtube
https://youtu.be/K_6OOLcghjg
On #Odysee
https://odysee.com/@YetanotherSysAdmin:0/Using-Bastille-to-create-Jails-on-FreeBSD:2
lo_if="lo1"
ext_if="vmx0"
jail_if="vmx0bridge"
#set block-policy return
scrub in on $ext_if all fragment reassemble
set skip on lo
set skip on $jail_if
table <jails> persist
nat on $ext_if from <jails> to any -> ($ext_if:0)
#nat on $ext_if from $jail_if:network to any -> ($ext_if)
#nat on $jail_if from $jail_if:network to any -> ($jail_if)
#nat on $lo_if from $jail_if:network to any -> ($lo_if)
rdr-anchor "rdr/*"
#block in all
pass out quick keep state
#antispoof for $ext_if inet
pass in inet proto tcp from any to any port ssh flags S/SA keep state
pass in on $ext_if inet proto icmp to ($ext_if) icmp-type { unreach, redir, timex, echoreq }
pass in on $ext_if inet proto icmp to ($jail_if) icmp-type { unreach, redir, timex, echoreq }
pass in on $jail_if inet proto icmp to $jail_if:network icmp-type { unreach, redir, timex, echoreq }
BastilleBSD can now create jails with static MAC addresses, and finally got rid of that pfctl call when NAT wasn't use
But that's not all, https://github.com/BastilleBSD/bastille/releases/tag/0.12.20250111
Working on FreeBSD is always a pleasure. When I need to make a change to a production jail, using BastilleBSD, I clone it in a flash, make the changes, and test them. If they work, I can promote that jail to production or discard the test one and apply the changes.
A way of working that, in my opinion, is both safe and efficient.
I don’t know if this is my lab or anything else, but #Wireguard is faster than #OpenVPN on #IPv6.
On #IPv4 it’s almost the same.
But I prefer WireGuard for this reason on my setup.
#FreeBSD #jail #bastilleBSD
It looks like iocage has been abandoned and I've found Bastille to have some advantages over it.
I tried to look up a way to migrate my jails to Bastille but so far everything includes exporting them from one system to another. Anyone know if I can do this on one system?
It seems that I should, given that both programs just manage the jails, but iocage uses a json file instead of the normal jail config and I'm not exactly sure what it's doing.
@acirep Hmm, I thought that maybe #BastilleBSD has a custom way of starting services which reimplements /etc/rc and forgets to source /etc/defaults/rc.conf. That's not the case, however. I don't know what's causing this behavior.
Well I've tested #Syncthing on my #FreeBSD server and it runs up perfectly in a #BastilleBSD #Jail and syncs with my Ubuntu server and my laptop plus Fairphone 4. So that's another thing off my list. Eventually I will wipe beastie and fit new drives for os and data and set everything up permanently and decommission the old celeron Ubuntu server. I've just to play a little bit more on Beastie until I'm 100% happy.
Ahh neat ! Might not sound like much to you but I've been playing with #BastilleBSD jails on #FreeBSD . I've got several running successfully each with their own IP. Today's test was to see if I could successfully export one, then delete it. Yep you guessed it , Then see if I could successfully import it and it still work. Did it work I hear you ask ?
Of course it did and I'm well chuffed. I know I'm easily pleased.
#RunBSD
Updated instructions for installing HA-Core 2025.5 in a FreeBSD jail: https://blog.brendans-bits.com/posts/2024/home-assistant-2024.5-jail/
Big thanks go to @jan for making it possible to install a new dependency (python-isal) and to @stefano for hosting brew.bsd.cafe where the homeassistant rc script is now located.
Any comments, suggestions, or corrections - please let me know.
Escape the cloud: Own your e-mail.
Make your own E-Mail server - FreeBSD, OpenSMTPD, Rspamd and Dovecot included - Part 1