"Atomic Configuration" ( https://nicmx.github.io/Jool/en/config-atomic.html#nat64 ) shows the example configuration for NAT64, but actually it is not feasible.
This configuration contains a BIB for TCP port 80 as following:
{
"protocol": "TCP",
"ipv6 address": "2001:db8::1#80",
"ipv4 address": "192.0.2.1#80"
}, {
but the configuration of pool4 contains an entry for TCP having only 61001-62000 port ranges.
{
"comment": "mark, port range and max-iterations are optional.",
"protocol": "TCP",
"prefix": "192.0.2.1/32"
}, {
Jool requires that incoming IPv4 packets must match any pool4 entries. https://github.com/NICMx/Jool/blob/master/src/mod/common/steps/filtering_and_updating.c#L526
Therefore the BIB mentioned above is not workable and that's why I think the configuration is not feasible.
"Atomic Configuration" ( https://nicmx.github.io/Jool/en/config-atomic.html#nat64 ) shows the example configuration for NAT64, but actually it is not feasible.
This configuration contains a BIB for TCP port 80 as following:
but the configuration of pool4 contains an entry for TCP having only 61001-62000 port ranges.
Jool requires that incoming IPv4 packets must match any pool4 entries. https://github.com/NICMx/Jool/blob/master/src/mod/common/steps/filtering_and_updating.c#L526
Therefore the BIB mentioned above is not workable and that's why I think the configuration is not feasible.