If you installed Jool’s Debian package, chances are your distribution manages daemons by way of systemd or System V. Jool’s Debian package ships with systemd unit files and System V scripts you can use to enable Jool automatically after every boot.
If you did not install Jool’s Debian package, you’re in for a bit more trouble. You can download our Debian unit files or scripts and adapt them to your needs.
This document explains how to do both of these.
First, provide a configuration file in
/etc/jool/. You can find some examples in
Once you’re set, try your service out:
The service creates the instance in the global network namespace. It’s a perfectly average instance, so you can query or further tweak it normally:
(But any changes meant to be persistent need to be included in the configuration file.)
That’s all. If the service is configured correctly, it will start automatically on every boot.
First, figure out whether you’re using systemd or System V, and whether you need an SIIT or a NAT64.
- This is Debian’s SIIT systemd unit file. (It probably needs to be renamed as
- This is Debian’s NAT64 systemd unit file. (It probably needs to be renamed as
- This is Debian’s SIIT System V script. (It probably needs to be renamed as
- This is Debian’s NAT64 System V script. (It probably needs to be renamed as
Grab the one you need and adapt it to your needs. To wit, the only thing you might need to modify is the path to the jool userspace client binary. In the files above it’s
/usr/bin/jool, but your installation might have likely placed them in