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 [--tcp] [--udp] [--icmp] ( [--display] [--numeric] [--csv] | --count )
--display: The session tables are printed in standard output. This is the default operation.
--count: The number of entries per session table are printed in standard output.
||If present, the command operates on the TCP table.|
||If present, the command operates on the UDP table.|
||If present, the command operates on the ICMP table.|
||By default, the application will attempt to resolve the names of the remote nodes talking in each session. If your nameservers aren’t answering, this will slow the output down.
||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.
--icmp are not mutually exclusive. If neither of them are present, all of the tables are displayed.
ipv6client.mx makes two HTTP requests and a ping to example.com.
Fall back to display all protocols, resolve names, console format:
Filter out UDP and ICMP, do not query the DNS, console format:
Do not resolve names, CSV format:
Just display the number of records of every table: