Basic SIIT Run
This document explains how to run Jool in stock SIIT mode. Follow the link for more details on what to expect.
Software-wise, only a successful install of Jool’s kernel module is required. The userspace application is out of the scope of this document on purpose.
In case you’re wondering, you can follow along these tutorials using virtual machines or alternate interface types just fine (Jool is not married to physical “ethX” interfaces).
You don’t need all the nodes shown in the diagram to follow along; you can get away with only A, T and V; the rest are very similar to A and V and are shown for illustrative purposes only.
We will pretend I have address block 198.51.100.8/29 to distribute among my IPv6 nodes.
Jool requires T to be Linux. The rest can be anything you want, as long as it implements the network protocol it’s connected to. You are also free to configure the networks using any manager you want.
For the sake of simplicity however, the examples below assume every node is Linux and everything is being configured statically using the well-known
ip command (and friends). Depending on your distro, your mileage might vary on how to get the network manager out of the way (assuming that’s what you want). Just to clarify, the point of
service network-manager stop below is to claim control over your interface addresses and routes (otherwise the
ip commands might be ineffectual).
Also to simplify, routing will be reduced to default all unknown traffic towards T. Note that there is nothing martian about anyone’s configuration otherwise.
This is nodes A through E:
Nodes V through Z:
Because we haven’t turned T into a translator yet, nodes A through E still cannot interact with V through Z, but you might want to make sure T can ping everyone before continuing.
Next, enable forwarding on T.
These sysctls make sense conceptually, but Jool doesn’t actually depend on them, currently.
What happens is, if you omit them in kernels 3.5 and below, everything will seem to work, but Linux will drop some important ICMP traffic. Skipping them in kernels 3.6 and above doesn’t actually yield known adverse consequences.
Whether this inconsistency is a bug in older or newer kernels is a rather philosophical topic. On the other hand, Jool 4.0 will almost certainly require forwarding, so you might as well start preparing your scripts.
The only caveat you need to keep in mind before inserting Jool is that you need to get rid of receive offloads in the translating machine. Do that by means of
(If it complains it cannot change something, keep in mind it can already be off; run
sudo ethtool --show-offload [interface] to figure it out.)
This is the insertion syntax:
user@T:~# /sbin/modprobe jool_siit \ [pool6=<IPv6 prefix>] \ [blacklist=<IPv4 prefixes>] \ [pool6791=<IPv4 prefixes>] \ [disabled]
See Kernel Module Options for a description of each argument. The following suffices for our sample network:
user@T:~# /sbin/modprobe jool_siit pool6=2001:db8::/96
That means the IPv6 representation of any IPv4 address is going to be
2001:db8::<IPv4 address>. See below for examples.
If something doesn’t work, try the FAQ.
Try to ping A from V like this:
Then ping V from A:
How about hooking up a server in X and access it from D:
Then maybe another one in C and request from W:
Revert the modprobe using the
-r flag to shut down Jool:
More complex setups might require you to consider the MTU notes.
Please note that none of what was done in this tutorial survives reboots! Documentation on persistence will be released in the future.