From Jool’s point of view, sessions mostly exist so the NAT64 can decide when BIB entries should die. You can also use them to know exactly who is speaking to your IPv6 nodes.
Each BIB entry is a mapping, which describes the IPv4 name of one of your IPv6 services. For every BIB entry, there are zero or more session entries, each of which represents an active connection currently using that mapping.
You can use this command to get information on each of these connections.
jool session display [PROTOCOL] [--numeric] [--csv] [--no-headers] PROTOCOL := --tcp | --udp | --icmp
Warning: Jool 3’s
PROTOCOLlabel used to be defined as
[--tcp] [--udp] [--icmp]. The flags are mutually exclusive now, and default to
The session table that corresponds to the
PROTOCOL protocol is printed in standard output.
||Operate on the TCP table. This is the default protocol.|
||Operate on the UDP table.|
||Operate on the ICMP table.|
||Print the table in Comma/Character-Separated Values format. This is intended to be redirected into a .csv file.
Because every record is printed in a single line, CSV is also better for grepping.
||Print the table entries only; omit the headers. (Table headers exist only on CSV mode.)|
ipv6client.mx makes two HTTP requests and a ping to
Show the TCP table, resolve names, console format:
Show the TCP table, do not query the DNS, console format:
Do not resolve names, CSV format: