No -- I don't believe that's a valid IPv6 address. We just ran some iperf3 tests between two servers on our network 2602:fcad:1::12 <-> 2602:fcad:1:ffff::ffff. Here's what showed up in nfdump (our Netflow collector). I'm not seeing an obvious pattern on how the addresses are being mangled.

You mean that for SRC_IP you expect it to be "2602:fcad:2:fffe:5054:ff" and not "14d:63f:2602:fcad:2:fffe:5054:ff" ?

PR https://github.com/vyos/vyos-1x/pull/2728

PR https://github.com/vyos/vyos-1x/pull/2728

PR https://github.com/vyos/vyos-1x/pull/2729

Related to the list provided in https://vyos.dev/T5706 ?

It is more of a question for Jool.
Or you can use a range of required ports that aren't used by the system

I've tinkered with this a bit , but a problem I have is that I need multiple ip addresses on the outgoing interface(s). I understand that Jool takes all ports, so It's needed for everything to work properly.
On my own WAN interface, this is not a problem, I can just assign another ip from my ISP.

PR https://github.com/vyos/vyos-1x/pull/2724

vyos@r4:~$ add system image latest

Removing 1.3 backport as it's not trivial. Implementation depends on python3-pyhump (not available and must be self build) and also on vyos.opmode framework which does not exist for 1.3 equuleus

My bad, I had misconfigured DNS on this test VM. It's now working as expected. Will there be a way to wrap this in an add system image command?

Thank you for the report.

PR for 1.5 https://github.com/vyos/vyos-1x/pull/2716

I start to think that this card requires an out-of tree vendor driver which is not going to be added by us.

Fixed via podman update - upstream bug