Networks the host controls
How JailOps networks jails without a bridge or a DHCP server. The host hands out addresses, gives every jail a link of its own and routes between them, so jails are kept apart. What you get, what you can do and what does not pass between jails.
The idea
The host is the router.
A network in JailOps is an address range with an uplink. Every jail gets an address from the range, written into its specification, and a private link to the host. The host answers on that link as the gateway and routes everything: from a jail to the internet, from the internet to a jail, and from one jail to another.
There is no bridge to design, no DHCP server to run and nothing to configure on the host but forwarding. The host is the only thing the jails can reach directly, so the host is where you decide what they can do.
A network in one command
Then a project and a jail.
$ jailops network create office --ipv4 192.0.2.1/24 --uplink em0 --nat $ jailops project create shop $ jailops network grant office --project shop $ jailops storage grant default --project shop $ jailops create site --project shop --image freebsd-15-1 --network office --storage default --start $ jailops network leases office
--nat translates what leaves through the uplink. jailops network leases lists who has which address. For IPv6 add a prefix: IPv6 and cloud setups.
Jails kept apart
Each jail has a link of its own.
Two jails never share a network segment, so:
- They cannot see each other's traffic. A jail that captures packets sees its own and nobody else's.
- They cannot poison each other. The ARP, neighbour, router advertisement and DHCP packets of a jail go no further than the host's end of its own link. A forged one changes nothing outside that jail.
- They cannot take each other's addresses. The host routes an address to the one link of the jail that owns it, and the jail's firewall drops what it sends from another address.
An address that no jail has is never sent out of the uplink: the host answers with an error.
Letting them talk
As far as the firewall allows.
What passes between two jails is what both jails' firewall policies allow, and jailops firewall test tells you before you try it. The host is an end like any other: allow out tcp to host port 443 lets a jail reach a service on the host.
$ jailops firewall test --from jail:web --to jail:db --port 5432What does not pass
Layer 2 stays on the host.
Because jails do not share a segment, traffic that depends on one does not go from one jail to another: multicast, mDNS, VRRP and CARP, and other protocols that are not IP. Services that need to find each other use addresses or names: the jails of a project reach each other as db.shop.internal, or just db (Names for jails).
More articles
Jail updates without cron
Replace the nightly script that upgrades every jail: automatic jail upgrades per image, with a health check, a rollback and a record of every run, what they leave alone, and how a new FreeBSD release comes in.
Read the article: Jail updates without cronJail search and shell
Ctrl+K, a few letters, Shift+Enter: find a jail by name, label or app and open its shell. Labels that filter the jail list, bash in new jails, and the jailops command next to every step.
Read the article: Jail search and shellGetting started with the JailOps CLI
Root on the host, the command line and nothing else: install JailOps, build an image, create a network and a jail, reach it by name, snapshot it, open a port and install an app.
Read the article: Getting started with the JailOps CLIJailOps on a netcup server, with IPv6 that stays up
A /64, a router pair and a FreeBSD default that drops their probes. How every jail gets its own IPv6 address on netcup, and the one sysctl that ends the random unreachable alerts.
Read the article: JailOps on a netcup server, with IPv6 that stays upOne small cloud server, many services, solid IPv6
Run your database, web tier and workers on one low-cost server, each jail with its own IPv6 address, and fix the alerts a shared /64 causes with one sysctl.
Read the article: One small cloud server, many services, solid IPv6Write your own app: memcached, from package to catalog
Turn a small FreeBSD package into a JailOps app: the definition line by line, the offline check, a local install, the five traps, and the pull request that puts it in the catalog.
Read the article: Write your own app: memcached, from package to catalogFrom catalog to running service in one command
Install nginx from the app catalog with one command, see each of its steps, and find the data, the configuration, the logs and the snapshot afterwards.
Read the article: From catalog to running service in one commandA firewall you can read
Policies, address sets and jails by name (jail:web), each with a comment, so the firewall can be reviewed by someone who did not write it.
Read the article: A firewall you can readPostgreSQL and git, closed except for who needs them
Close a database and a git server, then let in exactly the web jail and the office, with a comment on every entry.
Read the article: PostgreSQL and git, closed except for who needs themProjects are boundaries
A project is a boundary. Another project is an external host, so only addresses cross it, written out on both sides. Why that is simpler to review, and what a project does not isolate.
Read the article: Projects are boundariesThe life of a jail
A jail starts at boot only when you declared it with --autostart. Why JailOps does it this way, how the order is decided, and how to see it with jailops boot.
Read the article: The life of a jailTab completion for jailops
Press Tab and get the names of your jails, networks and firewall policies, even on another host. How to install and turn on completion in bash, zsh and fish.
Read the article: Tab completion for jailopsTest the firewall before you trust it
Ask the firewall whether a connection would pass, and why, before you try it. Read the answer, put it in a script, and know what it cannot tell you.
Read the article: Test the firewall before you trust itSee a connection before it happens
Pick a From and a To, a protocol and a port, press Run, and see the connection flow through the firewall: what passes, what stops it, and which rule decides.
Read the article: See a connection before it happensLimit what a jail can use
Give a jail a ceiling for memory, processes, CPU, disk, firewall states and bandwidth, one command each, and know what happens when it reaches it.
Read the article: Limit what a jail can useStop every jail cleanly when the host shuts down
A host that reboots should stop its databases before it stops the disks. How JailOps stops the jails in order, and how to start them in order again.
Read the article: Stop every jail cleanly when the host shuts downOne line in pf.conf
The host's firewall stays yours. JailOps asks for one line, and everything for the jails lives below it.
Read the article: One line in pf.confWhat the host tells you by itself
A pool that reports an error, an uplink that goes down, a jail that reaches a limit: they show up in the event stream by themselves.
Read the article: What the host tells you by itselfVolumes: data that outlives a jail
Keep the data in a volume and the jail disposable. One volume can be attached to several jails, has its own snapshots and its own backup.
Read the article: Volumes: data that outlives a jailBack up volumes once
One copy of a volume, however many jails use it. Leave volumes out when you want to, bring them back with the jail.
Read the article: Back up volumes onceA private Docker registry
A registry of your own with users in a file: one jail, docker-registry and docker-auth, htpasswd for the passwords, the images on a volume.
Read the article: A private Docker registryNames for jails
A jail is reached by its name inside its project: db.shop.internal, or just db. Create a jail and its name is there; delete it and the name is gone.
Read the article: Names for jails
Try it on one server.
Try the console from the screenshots, install on a clean FreeBSD 15.1 machine, or add JailOps to a host you already run.