Jool has a _feature_ relating to an underlying RFC6052, that required that buts 64-71 be zero. (ref: https://github.com/NICMx/Jool/issues/174)
If you supply a source prefix that has these lower bits set, then jool will fail to accept the config, but vyos only reports an error.
e.g.
# compare + nat64 { + source { + rule 10 { + source { + prefix "64:2001:db8:101:101::/96" + } + translation { + pool 10 { + address "192.0.2.1" + port "1-65535" + } + } + } + } + }
when you commit, you get an error like this:
# commit comment lol Failed to set jool instance instance-10 [[nat64]] failed Commit failed [edit]
and if you drop to a shell and try to run this yourself, it explains why:
# jool -i instance-10 file handle /run/jool/instance-10.json Error: The kernel module returned error 22: The u-bit is nonzero; see https://github.com/NICMx/Jool/issues/174. Will cancel the operation. Use --force to override this.
could we do some input validation t oreject the commit if the 64-71 bits are non zero?