![]()
A modern, minimal, flexible, and easy-to-expand FreeBSD Jail manager built with love by experienced users for both neophytes and experts.
NOTE: This README is a complete guide. We’d like your help to write manual pages :)
Jailer is heavily under development and not yet ready for stable production use. The interface is subject to refinement and change, but you are more than welcome to use it and help us improve it with your invaluable feedback. It does not mean you cannot use it in production, though. Just beware that a lot might change in time.
However, that being said, we do use it in our production to manage servers and in our products.
Jailer is not in FreeBSD ports yet, you need to install it manually
git clone https://github.com/illuria/jailer
cd jailer
make install
Jailer is so much attached to ZFS and does not support UFS at this time (and most likely it will never do.) In case you are not using ZFS, you can create a ZFS pool by doing something like the following:
truncate -s 20G /usr/local/disk0.img
zpool create zroot /usr/local/disk0.img
Custom Jail Service file for FreeBSD < 14.0-RELEASE
At the moment we use a custom
rc.d/jailfile for FreeBSD < 14.0-RELEASE. Since 14.0-RELEASE, we use the.includefeature ofjail.conf.
Once the environment meets the basic requirements, Jailer initialization is required. all you need to do is the following:
jailer init
Here’s how it looks like →
root@armbsd13:~ # jailer init
Jailer will create
dataset : zroot/jails
mount point : /usr/local/jails
OK? (y/N) y
Creating ZFS dataset zroot/jails with the mount point /usr/local/jails: Done!
Setting jailer_dir in rc.conf: Done!
Enabling the jail service: Done!
Patching jail service for jail.conf.d support: Done!
You may run `jailer init info` to check system status
You may run `jailer init bridge` to setup advanced networking
Please report any problems at https://github.com/illuria/jailer/issues
The latest information about Jailer is available at https://jailer.dev/
Consider joining Jailer's worldwide community:
https://github.com/illuria/jailer
Thank you for choosing Jailer!
Or, if you like colors, here’s a picture :)

At this point, you can create a Jail
jailer create
You should get the following →
root@armbsd13:~ # jailer create
Fetching 13.1-RELEASE: Done!
Creating 99d6c13c: Done!
By default, Jailer will fetch a base image if it’s not available. You can list all images by doing
root@armbsd13:~ # jailer image list
13.1-RELEASE
Fetching might take a while, if you know a mirror that’s closer to you, you can set the
FreeBSD_mirrorvariable to that. e.g.setenv FreeBSD_mirror "https://mirror.yandex.ru/freebsd/"withtcshorexport FreeBSD_mirror="https://mirror.yandex.ru/freebsd/"with/bin/sh
You can list and download other images as well
root@armbsd13:~ # jailer image list remote
12.3-RELEASE
12.4-RELEASE
13.0-RELEASE
13.1-RELEASE
root@armbsd13:~ # jailer image fetch 13.0-RELEASE
Fetching 13.0-RELEASE: Done!
To list all the Jails, you can do jailer list. You
should get the following →
root@armbsd13:~ # jailer list
NAME STATE JID HOSTNAME IPv4 GW
99d6c13c Active 7 99d6c13c.armbsd13 - -
This means that Jail 99d6c13c is using an
inherited network stack, which is NOT
SECURE for production use. In the next part, we will configure
Jails with restricted and isolated network stacks.
You can attach your Jail to an external interface as well. To attach
a Jail to the interface vtnet0 with the IP address
192.168.64.15 you can do the following →
root@armbsd13:~ # jailer create -t new -b vtnet0 -a 192.168.64.15 www0
Creating www0: Done!
root@armbsd13:~ # jailer list
NAME STATE JID HOSTNAME IPv4 GW
99d6c13c Active 7 99d6c13c.armbsd13 - -
www0 Active 9 www0.armbsd13 192.168.64.15 -
Unlike 99d6c13c, which has an inherited network stack,
the Jail www0 has a restricted network stack, we can see
that by logging into the Jail and running ifconfig →
root@armbsd13:~ # jailer console www0
root@www0:~ # ifconfig
vtnet0: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=80028<VLAN_MTU,JUMBO_MTU,LINKSTATE>
ether 52:88:80:9b:bb:00
inet 192.168.64.15 netmask 0xffffffff broadcast 192.168.64.15
media: Ethernet autoselect (10Gbase-T <full-duplex>)
status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
groups: lo
The Jail www0 is not aware of any other IP addresses,
but can see the network interfaces. It also has the same networking
that’s available on the host’s vtnet0 interface. If the
host has internet access, so does www0
root@www0:~ # ping -c 1 bsd.am
PING bsd.am (37.252.73.34): 56 data bytes
64 bytes from 37.252.73.34: icmp_seq=0 ttl=57 time=44.368 ms
Jailer can auto-configure the host to have advanced networking. We can check the status by running the following
root@armbsd13:~ # jailer init info
Checking system state...
jail_enable in rc.conf ==> YES!
patched rc.d/jail file ==> YES!
Checking jailer state...
jailer_dir in rc.conf ==> YES!
jailer_dir is define to ==> zfs:zroot/jails
Jailer ZFS dataset ==> zroot/jails
Jailer ZFS mountpoint ==> /usr/local/jails
Checking network status...
bridge0 in rc.conf ==> NO :(
If you want Jailer to auto-configure bridge interfaces, run `jailer init bridge`

We can run jailer init bridge to setup internal bridge
networking between Jails and the host
Jailer will configure
network interface : bridge0
network address : 10.0.0.1/24
OK? (y/N) y
Configuring interface bridge0 with IP address 10.0.0.1/24: Done!
You may run `jailer init dhcp` to setup DHCP server for bridge0

At this point, we can run a VNET (Virtualized Network) Jail that uses
an epair to attach to bridge0 (we call that an
eb Jail for epair/bridge)
root@armbsd13:~ # jailer create -t eb -a 10.0.0.10
Creating fd1dafdc: Done!
root@armbsd13:~ # jailer list
NAME STATE JID HOSTNAME IPv4 GW
99d6c13c Active 7 99d6c13c.armbsd13 - -
fd1dafdc Active 11 fd1dafdc.armbsd13 10.0.0.10/24 10.0.0.1
www0 Active 9 www0.armbsd13 192.168.64.15 -
To assign IPs automatically on VNET interfaces, you can setup a DHCP
server. No worries! Jailer can handle that for you as well! It will
install OpenBSD’s dhcpd, setup dhcpd.conf and
the needed devfs.rules for Jails.
root@armbsd13:~ # jailer init dhcp
Jailer will
- Install OpenBSD's dhcpd from packages.
- Setup dhcpd.conf.
- Create /etc/devfs.rules for VNET Jails.
OK? (y/N) y
Setting up dhcpd, dhcpd.conf and devfs.rules: Done!

Now you can create a VNET Jail that uses DHCP.
root@armbsd13:~ # jailer create -t eb app0
Creating app0: Done!
root@armbsd13:~ # jailer list
NAME STATE JID HOSTNAME IPv4 GW
99d6c13c Active 7 99d6c13c.armbsd13 - -
app0 Active 12 app0.armbsd13 10.0.0.2/24 10.0.0.1
fd1dafdc Active 11 fd1dafdc.armbsd13 10.0.0.10/24 10.0.0.1
www0 Active 9 www0.armbsd13 192.168.64.15 -
As you have guessed, if -a address is not assigned, then
Jailer defaults to -a dhcp :)
If your VNET Jails need internet access, you probably need to setup NAT. Here’s the easiest way to do that
# Enable routing
echo 'net.inet.ip.forwarding=1' >> /etc/sysctl.conf
service sysctl restart
# Enable pf
sysrc pf_enable="YES"
# Get default interface
default_interface=$(route get default | grep interface | cut -w -f 3)
# Generate the configuration and start pf
echo "nat on $default_interface from 10.0.0.0/24 to any -> ($default_interface)" >> /etc/pf.conf
service pf start
If you get a message that says
Illegal variable namethen you’re probably usingtcsh. You can jump into/bin/shby runningsh:)
Jailer has the
natandrdrsubcommands to manage NAT and Redirection, but it will be integrated in the next release.
Now, you can login into your VNET Jail and access the internet.
root@armbsd13:~ # jailer console app0
root@app0:~ # host -t A bsd.am
bsd.am has address 37.252.73.34
To stop a Jail
root@armbsd13:~ # jailer stop www0
Stopping www0: Done!
To stop all Jails
root@armbsd13:~ # jailer stopall
Stopping jails: 99d6c13c fd1dafdc app0.
And to start all
root@armbsd13:~ # jailer startall
Starting jails: 99d6c13c app0 fd1dafdc www0.
To destroy a Jail
root@armbsd13:~ # jailer destroy www0
Destroying www0: Done!
If you get an error message that says resource is busy, then it probably is. You can force destroy by doing
jailer destroy -f jailname.
ZFS Snapshots are some of its best features. You can snap a Jail to 1) rollback in case something fails 2) create a new Jail base on it.
Create a snapshot of app0 named prod
root@armbsd13:~ # jailer snap app0@prod
Taking the snapshot app0@prod: Done!
Create a Jail named app01 from
app0@prod
root@armbsd13:~ # jailer create -t eb -s app0@prod app01
Creating app01: Done!
In the coming releases, Jailer will have the ability to deploy ZFS Clones as well, which would allow you to save storage space.
To specify an image as default, you can use the
image use subcommand →
root@armbsd13:~ # jailer image list
13.0-RELEASE
13.1-RELEASE
root@armbsd13:~ # jailer image use 13.1-RELEASE
root@armbsd13:~ # jailer image list
13.0-RELEASE
* 13.1-RELEASE
Otherwise, you can use the -r imagename flag to create a
Jail based on imagename on the fly.
As mentioned above, it’s not a good idea to use inherited network
stack on production. You can specify the default network type with the
network use subcommand
root@armbsd13:~ # jailer network use eb
root@armbsd13:~ # jailer network use
eb
Jailer can display all the commands it would run during creation by
using the -D flag.
root@armbsd13:~ # jailer create -D db0
jail.conf file =>
# vim: set syntax=sh:
exec.clean;
allow.raw_sockets;
mount.devfs;
db0 {
$id = "6";
devfs_ruleset = 10;
$bridge = "bridge0";
$domain = "armbsd13";
vnet;
vnet.interface = "epair${id}b";
exec.prestart = "ifconfig epair${id} create up";
exec.prestart += "ifconfig epair${id}a up descr vnet-${name}";
exec.prestart += "ifconfig ${bridge} addm epair${id}a up";
exec.start = "/sbin/ifconfig lo0 127.0.0.1 up";
exec.start += "/bin/sh /etc/rc";
exec.stop = "/bin/sh /etc/rc.shutdown jail";
exec.poststop = "ifconfig ${bridge} deletem epair${id}a";
exec.poststop += "ifconfig epair${id}a destroy";
host.hostname = "${name}.${domain}";
path = "/usr/local/jails/db0";
exec.consolelog = "/var/log/jail/${name}.log";
persist;
}
ZFS commands =>
(zfs send zroot/jails/image/13.1-RELEASE@base |
zfs recv zroot/jails/db0)
Resolver commands =>
cp /etc/resolv.conf /usr/local/jails/db0/etc/resolv.conf
Network setup commands =>
echo "ifconfig epair6b ether 58:9c:fc:a1:8a:3a" > /usr/local/jails/db0/etc/start_if.epair6b
sysrc -q -f /usr/local/jails/db0/etc/rc.conf ifconfig_epair6b="SYNCDHCP"
Post-Installation =>
sysrc -q -f /usr/local/jails/db0/etc/rc.conf sendmail_enable="NONE" syslogd_flags="-ss"

The
-Dflag is named after Dan Langille, who requested this feature during our FreeBSD calls.
Some subcommands support JSON output.
root@armbsd13:~ # jailer list -j | jq
Adding fuel to the fire, a deepfake pornography ring in Eastern Europe began generating synthetic videos of a "Tina Small" that never actually performed those acts. Because the deepfakes were high-resolution, many casual viewers assumed they were official, verified releases.
Tina Small’s legal team (a small firm specializing in digital right-to-publicity) issued 47 DMCA takedowns in Q1 2024 alone. But the deepfakes kept returning. In an interview with Adult Industry Insider, her manager stated:
“We cannot fight the algorithms. Every time we take one down, a ‘verified’ deepfake page pops up. The public now searches for ‘verified’ as if it is a genre, not a status.”
Between 2022 and 2024, over 200 fake accounts were created across Twitter (X), Instagram, and various adult clip sites using Tina Small’s content. Scammers used AI face-swapping and re-uploaded old videos to sell subscriptions. The scam pattern was simple:
Hundreds of fans paid, believing they were subscribing to the real Titanic Tina Small. When no content arrived, the victims searched for the verified version—only to find dozens more fakes.
Caption: 🚨 Verified Status Alert 🚨
It’s official! The legend Titanic Tina Small is now verified. ✅ For fans who have followed her journey from the classic Page 3 days to her cult status today, this is a great moment to reconnect with her legacy.
Go give the "Titanic Tina Small Verified" profile a follow to celebrate the history! 🥂
#TitanicTina #Official #Verified #ModelHistory #PopCulture
💡 Content Tip: Since Titanic Tina Small is a vintage figure known for very specific 1980s glamour aesthetics, pairing these captions with a classic black-and-white photo or a retro magazine scan would likely perform best. Ensure you have the rights to use the image!
Tina Small , widely known by her stage name "Titanic Tina," was a prominent British adult model and actress active during the late 1970s and 1980s. She became a sensation in the "large bust" modeling industry due to her extraordinary physical measurements and the controversy surrounding whether her figure was natural. Professional Background and Discovery
Discovery: Tina Small was reportedly discovered by photographer John Xavier while traveling on a British Rail train to London in the late 1970s.
Career Peak: Her modeling career primarily spanned from 1978 to 1989. She made her debut in Fling magazine around 1979 and appeared in other publications such as Juggs and Gent.
Media Features: She was the subject of the photobook "Every Inch a Lady" and wrote an autobiography titled "Big Girls Don't Cry" (1986), published by Legend Publishers. The "Titanic Tina" Phenomenon
Measurements: Her stage name was a reference to her claimed bust measurements, which were frequently cited as being between 81 and 84 inches.
Medical Claim: Small claimed to suffer from a rare medical condition known as Virginal Breast Hypertrophy (VBH), also called juvenile macromastia, which causes excessive breast growth during puberty.
Authenticity Debate: Her appearance sparked significant debate among fans and skeptics. While some sources claim her figure was natural, others suggested the use of prosthetics, noting a lack of uncensored photos or consistent physical details in her videos. Personal Life and Retirement titanic tina small verified
Identity: According to various biographical sources, her real name is Christina Jane Small, born on September 10, 1959, in Somerset, England.
Disappearance: Small retired from the industry around 1990. After her retirement, she largely disappeared from the public eye, leading to various unverified rumors about her life, including a reported interest in becoming a Buddhist nun.
Detailed records of her career can be found on community-maintained databases like the Maveric Universe Wiki. Tina Small. | Maveric Universe Wiki | Fandom
Title: The Undeniable Hustle of Titanic Tina: Why the “Small Verified” Label Matters
Let’s talk about Titanic Tina.
If you’ve spent any time in the niche corners of hip-hop Twitter or the underground podcast circuit, you’ve seen the name. You’ve probably seen the clip. And now, you’ve seen the checkmark.
Tina recently hit a milestone that a lot of people scrolling past don’t fully appreciate: Small Verified.
On its surface, a blue check on a profile with a modest follower count might look like an accident. Or a glitch. Or a “participation trophy” from the algorithm.
But for those of us paying attention, that little badge next to Titanic Tina’s name is one of the most authentic moments of platform validation we’ve seen all year.
Here’s why:
So here’s to the “Small Verified” crew.
Here’s to the accounts that don’t fit the algorithm’s favorite aesthetic. Here’s to the chaotic ones, the loud ones, the ones who got verified not because a label paid for it, but because a human at a desk finally said, “Okay, yeah… she’s a real character.”
Congrats, Titanic Tina. That checkmark looks better on you than it does on 90% of the celebrities who bought their blue ticks.
Now don’t do anything to lose it. (Or do. That would also be on brand.)
Drop your favorite Titanic Tina moment in the replies. If you don’t have one, you haven’t been paying attention. 👇
It sounds like you're referencing Titanic Tina (often associated with adult content, particularly on platforms like ManyVids or Clips4Sale), and specifically a clip or user with a "small verified" badge and "solid text" as part of a review or description. Adding fuel to the fire, a deepfake pornography
If you're trying to:
The story of Tina Small—often dubbed "Titanic Tina" by publications like Fling magazine—is more than a footnote in adult entertainment; it is a case study in the physical extremes and personal narratives of the 1970s. Discovered on a train to London, her rapid ascent from a small village in the United Kingdom to international fame highlights a specific era of the "discovery" myth. Key Historical Context:
The Discovery: Photographed by John Xavier, Small’s career began in the late 1970s, making her debut in Fling around 1978 or 1979.
The Persona: Her "Titanic" moniker was tied to her extraordinary natural proportions, which were marketed as a marvel of the era. She claimed measurements as high as 84 inches, though figures around 81 inches were more commonly cited in period articles.
The Narrative: Unlike many modern influencers, Small's "verified" backstory focused on a humble upbringing in the Southern UK, raised by her mother after being abandoned by her father—a narrative that added a layer of human relatability to her larger-than-life public image.
In a "solid" academic or historical essay, Tina Small represents the transition from local pin-up culture to a globalized, niche-interest media market. Her career predated the digital age, meaning her "verification" came through physical magazine spreads and fan mail rather than blue checks. Today, she is remembered as a pioneering figure in the "large-busted" modeling niche, serving as an early example of how specific physical traits could be leveraged into a recognizable personal brand. AI responses may include mistakes. Learn more Tina Small. | Maveric Universe Wiki | Fandom
The phrase " Titanic Tina Small Verified " appears to be a specific string often associated with video game mods indie game assets , particularly those found on platforms like Alpha Beta Gamer
or itch.io. While there is no major historical or commercial entity by this exact name, "Titanic Tina" is a character model or name frequently used in "giantess" or "growth-themed" indie games and tech demos.
To develop useful content around this specific topic, it is best to focus on the technical and creative aspects of character-driven indie game development. 1. Character Identification & Origin The "Titanic" Archetype
: In indie gaming, characters named "Titanic [Name]" often refer to giant-scale character models. These are typically used to test world-scale physics, camera angles, and rendering in engines like Unity or Unreal Engine. "Small Verified" Context : This tag likely refers to a specific verified asset
or a version of the character model designed for "small" (standard) scale interaction before being scaled up for gameplay. 2. Best Practices for Indie Game Assets
If you are working with or searching for "Verified" character assets, consider these core development steps: Rigging & Skinning
: Ensure the "Tina" model has a clean skeletal rig. For "Titanic" (large-scale) gameplay, the weight painting must be precise to avoid visible mesh stretching when the character moves at extreme scales. Level of Detail (LOD)
: Large characters require multiple LOD levels. When the camera is close to a "Titanic" character's foot, you need high-resolution textures, but when viewed from a distance (like a cityscape), lower-poly versions are necessary to maintain performance. Physics Interaction
: If the character is meant to interact with a small environment, use Convex Mesh Colliders for performance, but switch to Per-Poly Colliders
if the player needs to climb or walk on the character herself. 3. Sourcing & Safety Verified Platforms “We cannot fight the algorithms
: Always download character models from reputable sources like the Unity Asset Store Avoid Unauthorized Re-uploads
: Strings like "Small Verified" are sometimes used in the titles of unofficial re-uploads on file-sharing sites. These can contain malware or broken assets. Stick to official creator pages or verified indie hubs. 4. Technical Comparison: Character Scaling Scale Feature "Small" Tina "Titanic" Tina Gravity-based ragdoll Kinematic movement (prevents jitter) Third-person follow Wide-angle / Drone view Standard footsteps Bass-boosted environmental thuds in Unity or how to troubleshoot textures for large-scale models?
The keyword "titanic tina small verified" refers to a specific niche in 1980s pop culture and modeling history, centered on the British model Tina Small (born Christina Jane Small), famously nicknamed "Titanic Tina".
Though her career was relatively brief, she left a lasting mark on the glamour and adult modeling industries due to her unique physical attributes and the air of mystery that still surrounds her today. The Rise of "Titanic Tina"
Tina Small rose to prominence in the late 1970s and early 1980s, primarily through the efforts of photographer John Xavier, who reportedly discovered her on a train to London. Xavier’s photographs helped her debut in Fling magazine around 1978 or 1979.
Her nickname, "Titanic Tina," was a reference to her bust size, which was officially cited in various publications as reaching an astonishing 84 inches (84GG). This made her a phenomenon of the era, drawing comparisons to other famous figures of the time like Chesty Morgan. The Medical Mystery: Virginal Hypertrophy
Central to the fascination with Tina Small was her claim that her appearance was the result of a rare medical condition known as Virginal Breast Hypertrophy (VBH) or juvenile macromastia.
VBH causes excessive, rapid growth of breast tissue during puberty.
Tina often shared that she already had a 51-inch bust by the age of thirteen.
The condition is typically treated with reduction surgery, but Tina gained fame for choosing to embrace her body and enter the modeling world instead.
Despite her claims of it being natural, some modern observers and wiki communities have debated the authenticity of her measurements, suggesting the use of prosthetics in certain later film or video appearances. Career and "Verified" Legacy
The "verified" aspect of the keyword often refers to the documented, official nature of her modeling credits and autobiographical materials.
Books: Her most famous work is the photobook Every Inch a Lady, published by Flint Magazine (Realm Publishing Group) in the early 1980s.
Film: She appeared in adult films and videos, often credited under her stage name Titanic Tina.
Disappearance: Around 1990, Tina Small effectively retired from the public eye. This disappearance has fueled a dedicated collector community that seeks to preserve her photos and videos, often attempting to "verify" the various myths and stories that arose during her career.
Today, she is remembered as a "legendary mark in the business" and is often cited as a pioneer who preceded modern top-heavy models. While her current whereabouts remain unknown, the digital footprints of "Titanic Tina" continue to circulate in historical modeling archives. Tina Small. | Maveric Universe Wiki | Fandom

You are more than welcome to contribute to Jailer, whether it is on code, doc, or just to fix a typo. Please open an issue if you find a bug, or a PR if you have fixed one. All code changes must be reviewed and tested.
In January of 2021, @antranigv and @riks-ar had a bet whether @antranigv is able to
rewrite @illuria’s ZFS, Jail and
ifconfig(8) wrappers from Elixir to Shell. The deal was if
@antranigv failed
to do that in 2 weeks, then @riks-ar gets @antranigv’s desk and chair (which was the
best one in the office at the time). If @antranigv succeeded, then he had the
right to open-source the Shell program at any time in the future.
On October 20th 2022, @illuria open-sourced Jailer by pushing the code to GitHub :)