Interacts with NAT64 Jool’s IPv4 transport address pool.
The IPv4 pool is the subset of the node’s transport addresses which are reserved to mask IPv6 nodes.
If pool4 is empty, Jool will try to mask packets using its own node’s assigned IPv4 addresses, and their default unused port ranges. See Notes.
jool --pool4 ( [--display] [--csv] | --add <PROTOCOLS> <IPv4-prefix> <port-range> [--mark <mark>] [--force] | --remove <PROTOCOLS> <IPv4-prefix> <port-range> [--mark <mark>] [--quick] | --flush [--quick] ) <PROTOCOLS> := [--tcp] [--udp] [--icmp]
--display: The pool’s records are printed in standard output. This is the default operation.
--add: Uploads entries to the pool. See notes.
--remove: Deletes entries from the pool.
--flush: Removes all entries from the pool.
--countoperation is no longer available in
The replacement can be found here.
||(absent)||Print the table in Comma/Character-Separated Values format. This is intended to be redirected into a .csv file.|
||0||Defines the mark of the entry being added or removed. Packets carrying mark n will only be translated using pool4 records with mark n. See below.|
||*||If present, the record being added or removed represents TCP transport addresses.|
||*||If present, the record being added or removed represents UDP transport addresses.|
||*||If present, the record being added or removed represents “ICMP transport addresses” (Addresses and ICMP identifiers, not ports).|
||-||Group of addresses you’re adding or removing to/from the pool. The length defaults to 32, so you typically add and remove addresses instead of prefixes.|
||1-65535 for TCP/UDP, 0-65535 for ICMP||Subset layer 4 identifiers (or ICMP ids) from the addresses which should be reserved for translation.|
||(absent)||If present, add the elements to the pool even if they’re too many.
(Will print a warning and quit otherwise.)
||(absent)||Do not cascade removal to BIB entries.
--icmp are not mutually exclusive. If neither of them are present, the records are added or removed to/from all three protocols.
Display the current addreses:
$ jool --pool4 --display (empty)
Add several entries:
# jool --pool4 --add 192.0.2.1 $ jool --pool4 --display 0 ICMP 192.0.2.1 0-65535 0 UDP 192.0.2.1 1-65535 0 TCP 192.0.2.1 1-65535 (Fetched 3 entries.) # jool --pool4 --add --tcp 192.0.2.2 7000-7999 # jool --pool4 --add --mark 1 --tcp 192.0.2.2 8000-8999 # jool --pool4 --add --tcp 192.0.2.4/31 $ jool --pool4 --display 0 ICMP 192.0.2.1 0-65535 0 UDP 192.0.2.1 1-65535 0 TCP 192.0.2.1 1-65535 0 TCP 192.0.2.2 7000-7999 0 TCP 192.0.2.4 1-65535 0 TCP 192.0.2.5 1-65535 1 TCP 192.0.2.2 8000-8999 (Fetched 7 entries.)
Remove some entries:
# jool --pool4 --remove --mark 0 192.0.2.0/24 0-65535 $ jool --pool4 --display 1 TCP 192.0.2.2 8000-8999 (Fetched 1 entries.)
Clear the table:
# jool --pool4 --flush $ jool --pool4 --display (empty)
You need to be aware that your NAT64 machine needs to reserve transport addresses for translation purposes. If something within it tries to open a connection from transport address
192.0.2.1#5000 and at the same time a translation yields source transport address
192.0.2.1#5000, evil things will happen.
In other words, you don’t want pool4’s domain to intersect with other port ranges (just like you don’t want other port ranges intersecting with other port ranges).
You already know the ports owned by any servers parked in your NAT64, if any. The other one you need to keep in mind is the ephemeral range:
$ sysctl net.ipv4.ip_local_port_range net.ipv4.ip_local_port_range = 32768 61000
Linux’s ephemeral port range defaults to 32768-61000. Therefore, Jool falls back to use ports 61001-65535 (of whatever primary global addresses its node is wearing) when pool4 is empty. You can change the former by tweaking sysctl
sys.net.ipv4.ip_local_port_range, and the latter by means of
--pool4 --add and
Say your NAT64’s machine has address 192.0.2.1 and pool4 is empty.
$ jool --pool4 --display (empty)
This means Jool is using ports and ICMP ids 61001-65535 of address 192.0.2.1. Let’s add them explicitely:
# jool --pool4 --add 192.0.2.1 61001-65535 # jool --pool4 --display 0 ICMP 192.0.2.1 61001-65535 0 UDP 192.0.2.1 61001-65535 0 TCP 192.0.2.1 61001-65535 (Fetched 3 samples.)
So, for example, if you only have this one address, but want to reserve more ports for translation, you have to substract them from elsewhere. The ephemeral range is a good candidate:
# sysctl -w net.ipv4.ip_local_port_range="32768 40000" # jool --pool4 --add 192.0.2.1 40001-61000 $ sysctl net.ipv4.ip_local_port_range net.ipv4.ip_local_port_range = 32768 40000 $ jool --pool4 --display 0 ICMP 192.0.2.1 40001-65535 0 UDP 192.0.2.1 40001-65535 0 TCP 192.0.2.1 40001-65535 (Fetched 3 samples.)
Jool is incapable of ensuring pool4 does not intersect with other port ranges; this validation is the operator’s responsibility.
Mark allows you to assign different IPv4 transport address ranges to different IPv6 clients.
Pool4 entries carrying mark n will only affect packets marked n. You can mark packets any way you want using standard iptables matching done in IPv6 prerouting.
$ # Packets from network 2001:db8:1::/64 will be masked using ports 10000-19999. # jool --pool4 --add 192.0.2.1 10000-19999 --mark 10 # ip6tables -t mangle -I PREROUTING -s 2001:db8:1::/64 -j MARK --set-mark 10 $ $ # Packets from network 2001:db8:2::/64 will be masked using ports 20000-29999. # jool --pool4 --add 192.0.2.1 20000-29999 --mark 20 # ip6tables -t mangle -I PREROUTING -s 2001:db8:2::/64 -j MARK --set-mark 20
Recognizing or narrowing down the IPv6 clients behind IPv4 transport addresses helps you create IPv4-based ACLs and preventing groups of clients from hogging up IPv4 transport addresses (therefore DOSing the NAT64 for other clients).
See this project as well.
--flush a pool4 entry, the BIB entries that match it become obsolete because the packets they serve are no longer going to be translated. This is because a pool4 match is a prerequisite for translation.
--quickis absent during a pool4 entry removal, Jool will also get rid of the now obsolete “slaves”. This saves memory, keeps the database consistent and optimizes BIB entry lookup during packet translations. The removal operation itself, however, is slower.
- On the other hand, when you do issue
--quick, Jool will only purge the pool4 entries, thereby “orphaning” its BIB entries. This can be useful if you know you have too many BIB entries and want the operation to succeed immediately, or more likely you plan to re-add the pool4 entry in the future. Doing so will enable the (still remaining) slaves again.
Orphaned slaves will remain inactive in the database, and will eventually kill themselves once their normal removal conditions are met (ie. once all their sessions expire).