Interacts with Jool’s Binding Information Base (BIB).
jool --bib [--tcp] [--udp] [--icmp] ( [--display] [--numeric] [--csv] | --count | --add <IPv4-transport-address> <IPv6-transport-address> | --remove <IPv4-transport-address> <IPv6-transport-address> )
--display: The BIB tables are printed in standard output. This is the default operation.
--count: The number of entries per BIB table are printed in standard output.
<IPv6-transport-address>into a static BIB entry, and uploads it to Jool’s tables.
Note that the
<IPv4-transport-address>component must be a member of Jool’s IPv4 pool, so make sure you have registered it there first.
--remove: Deletes from the tables the BIB entry described by
Within a BIB table, every IPv4 transport address is unique. Within a BIB table, every IPv6 transport address is also unique. Therefore, If you’re removing a BIB entry, you actually only need to provide one transport address. You can still input both to make sure you’re deleting exactly what you want to delete, though.
||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 name of the IPv6 node of each BIB entry. 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.|
--icmp are not mutually exclusive. If neither of them are present, the records are added or removed to/from all three protocols.
- 188.8.131.52 belongs to the IPv4 pool.
- The name of 6::6 is “potato.mx”.
- 6::6 already spoke to a IPv4 node recently, so the database will not start empty.
Display the entire database:
Publish a couple of TCP services:
Display the TCP table:
Same, but do not query the DNS:
Publish a UDP service:
Dump the database on a CSV file:
Display the number of entries in the TCP and ICMP tables:
Remove the UDP entry: