IPv6 Issues with thunderbolt-net driver?

=0A=
It appears that IPv6 is 'broken' when using thunderbolt-net connections.=0A=
ICMPv6 works.=0A=
=0A=
Repro=0A=
-------=0A=
- Take two machines each with debian on them with a thunderbolt TB4 connect=
ion.=0A=
- Ensure there are no IPTABLES filtering rules in place=0A=
- configure ssh to listen on all ports, all protocols=0A=
- Connect the two machines with a TB cable.=0A=
- Statically address each interface on each machine with an IPv6 address in=
 the same subnet=0A=
- ping machine 1 IPv6 from machine 2 (this will work)=0A=
- try to ssh from machine 1 to machine 2 using IPv6 (this will not work)=0A=
=0A=
note: this seems to affect other traffic other than SSH too (like ceph clus=
ter traffic)=0A=
This has been reproduced on promox ve 8 and vanilla debian 12 (by two peopl=
e)=0A=
=0A=
Also on the same machines i repeated the same steps with a direct connected=
 ethernet cable and had zero issues (in my mind this validates the basic co=
nfiguration is ok).=0A=
=0A=
This is my first time using a mailing list, so apologies if i have taken th=
e wrong approach.=0A=
=0A=
alex=0A=
=0A=