jool_siit eamt ( display [--csv] | add <IPv4-prefix> <IPv6-prefix> [--force] | remove <IPv4-prefix> <IPv6-prefix> | flush )
display: The EAMT is printed in standard output.
<IPv6-prefix>into an EAM entry, and uploads it to Jool’s table.
remove: Deletes from the table the EAM entry described by
flush: Removes all entries from the table.
If you want to add many EAM entries at once,
eamt addmight turn out to be very slow. If you run into this problem, try adding them through atomic configuration instead. (But this only works on Jool 4.1.6+, or the current master.)
||Print the table in Comma/Character-Separated Values format. This is intended to be redirected into a .csv file.|
||Upload the entry even if overlapping occurs. (See the next section.)|
Overlapping EAM entries
By default, EAMT entries are not allowed to overlap. You can use
adding to override this property. When overlapping EAMT entries exist, Jool picks based on longest match prefix.
|IPv4 Prefix||IPv6 Prefix|
192.0.2.8/29 better than
192.0.2.0/24, so it will get translated as
Notice this creates assymetry.
2001:db8:aaaa::9 gets translated as
192.0.2.9, which in turn gets translated as
2001:db8:bbbb::1. Depending on your use case, this can break communication.
Overlapping EAMT entries exist to help EAM coexist with IVI. Other use cases might arise in the future.
These examples below assume that the name of the Jool instance is “
Add a handful of mappings:
Display the new table:
Dump the database on a CSV file:
Remove the first entry:
Empty the table: