Sorry i should have included this because i know someone will ask....
root@pve2:~# ip6tables --list Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination ________________________________ From: Alex Balcanquall <[email protected]> Sent: Tuesday, September 5, 2023 12:08 PM To: Marco <[email protected]>; [email protected] <[email protected]> Subject: Re: IPv6 Issues with thunderbolt-net driver? I hope this helps? On each machine i used tcpdump -i <interfacename> ip6 Pve1 is source machine Pve2 is destination machine i see the ssh packet on pve1 dump i don't see the ssh packed from pve2 dump of course what i can't tell is 1. did the ssh packet hit the wire or not or got discarded by the driver after tcpdumpsaw 2. if the packet did hit the wire did pve2 see it and discard the packet before it got far enough up the stack to be seen by tcpdump... 3. and I am a little unclear how i could do that given this is a point to point connection of thunderbolt (i have seen classic IP so both a and b above) pve1 root@pve1:~# cat pve1.tcpdump 11:55:49.665770 IP6 xxxx:xxxx:830:81::81 > xxxx:xxxx:830:81::82: ICMP6, echo request, id 19484, seq 1, length 64 11:55:49.666154 IP6 xxxx:xxxx:830:81::82 > xxxx:xxxx:830:81::81: ICMP6, echo reply, id 19484, seq 1, length 64 11:55:50.667366 IP6 xxxx:xxxx:830:81::81 > xxxx:xxxx:830:81::82: ICMP6, echo request, id 19484, seq 2, length 64 11:55:50.667912 IP6 xxxx:xxxx:830:81::82 > xxxx:xxxx:830:81::81: ICMP6, echo reply, id 19484, seq 2, length 64 11:55:51.691357 IP6 xxxx:xxxx:830:81::81 > xxxx:xxxx:830:81::82: ICMP6, echo request, id 19484, seq 3, length 64 11:55:51.691949 IP6 xxxx:xxxx:830:81::82 > xxxx:xxxx:830:81::81: ICMP6, echo reply, id 19484, seq 3, length 64 11:55:52.715355 IP6 xxxx:xxxx:830:81::81 > xxxx:xxxx:830:81::82: ICMP6, echo request, id 19484, seq 4, length 64 11:55:52.715859 IP6 xxxx:xxxx:830:81::82 > xxxx:xxxx:830:81::81: ICMP6, echo reply, id 19484, seq 4, length 64 11:55:53.739355 IP6 xxxx:xxxx:830:81::81 > xxxx:xxxx:830:81::82: ICMP6, echo request, id 19484, seq 5, length 64 11:55:53.739712 IP6 xxxx:xxxx:830:81::82 > xxxx:xxxx:830:81::81: ICMP6, echo reply, id 19484, seq 5, length 64 11:55:54.723856 IP6 fe80::8e:95ff:fef1:621a > xxxx:xxxx:830:81::81: ICMP6, neighbor solicitation, who has xxxx:xxxx:830:81::81, length 32 11:55:54.723899 IP6 xxxx:xxxx:830:81::81 > fe80::8e:95ff:fef1:621a: ICMP6, neighbor advertisement, tgt is xxxx:xxxx:830:81::81, length 24 11:55:54.763353 IP6 xxxx:xxxx:830:81::81 > xxxx:xxxx:830:81::82: ICMP6, echo request, id 19484, seq 6, length 64 11:55:54.763722 IP6 xxxx:xxxx:830:81::82 > xxxx:xxxx:830:81::81: ICMP6, echo reply, id 19484, seq 6, length 64 11:55:59.851247 IP6 fe80::1a:44ff:fe65:dbe0 > fe80::8e:95ff:fef1:621a: ICMP6, neighbor solicitation, who has fe80::8e:95ff:fef1:621a, length 32 11:55:59.851687 IP6 fe80::8e:95ff:fef1:621a > fe80::1a:44ff:fe65:dbe0: ICMP6, neighbor advertisement, tgt is fe80::8e:95ff:fef1:621a, length 24 11:56:02.235174 IP6 xxxx:xxxx:830:81::81.60670 > xxxx:xxxx:830:81::82.ssh: Flags [S], seq 2237794262, win 65460, options [mss 65460,sackOK,TS val 2783492204 ecr 0,nop,wscale 7], length 0 11:56:03.243291 IP6 xxxx:xxxx:830:81::81.60670 > xxxx:xxxx:830:81::82.ssh: Flags [S], seq 2237794262, win 65460, options [mss 65460,sackOK,TS val 2783493212 ecr 0,nop,wscale 7], length 0 11:56:04.963688 IP6 fe80::8e:95ff:fef1:621a > fe80::1a:44ff:fe65:dbe0: ICMP6, neighbor solicitation, who has fe80::1a:44ff:fe65:dbe0, length 32 11:56:04.963726 IP6 fe80::1a:44ff:fe65:dbe0 > fe80::8e:95ff:fef1:621a: ICMP6, neighbor advertisement, tgt is fe80::1a:44ff:fe65:dbe0, length 24 11:56:05.259237 IP6 xxxx:xxxx:830:81::81.60670 > xxxx:xxxx:830:81::82.ssh: Flags [S], seq 2237794262, win 65460, options [mss 65460,sackOK,TS val 2783495228 ecr 0,nop,wscale 7], length 0 pve2 root@pve2:~# cat pve2.tcpdump 11:55:49.665477 IP6 xxxx:xxxx:830:81::81 > xxxx:xxxx:830:81::82: ICMP6, echo request, id 19484, seq 1, length 64 11:55:49.665503 IP6 xxxx:xxxx:830:81::82 > xxxx:xxxx:830:81::81: ICMP6, echo reply, id 19484, seq 1, length 64 11:55:50.667060 IP6 xxxx:xxxx:830:81::81 > xxxx:xxxx:830:81::82: ICMP6, echo request, id 19484, seq 2, length 64 11:55:50.667095 IP6 xxxx:xxxx:830:81::82 > xxxx:xxxx:830:81::81: ICMP6, echo reply, id 19484, seq 2, length 64 11:55:51.691134 IP6 xxxx:xxxx:830:81::81 > xxxx:xxxx:830:81::82: ICMP6, echo request, id 19484, seq 3, length 64 11:55:51.691157 IP6 xxxx:xxxx:830:81::82 > xxxx:xxxx:830:81::81: ICMP6, echo reply, id 19484, seq 3, length 64 11:55:52.715051 IP6 xxxx:xxxx:830:81::81 > xxxx:xxxx:830:81::82: ICMP6, echo request, id 19484, seq 4, length 64 11:55:52.715086 IP6 xxxx:xxxx:830:81::82 > xxxx:xxxx:830:81::81: ICMP6, echo reply, id 19484, seq 4, length 64 11:55:53.738964 IP6 xxxx:xxxx:830:81::81 > xxxx:xxxx:830:81::82: ICMP6, echo request, id 19484, seq 5, length 64 11:55:53.738990 IP6 xxxx:xxxx:830:81::82 > xxxx:xxxx:830:81::81: ICMP6, echo reply, id 19484, seq 5, length 64 11:55:54.722922 IP6 fe80::8e:95ff:fef1:621a > xxxx:xxxx:830:81::81: ICMP6, neighbor solicitation, who has xxxx:xxxx:830:81::81, length 32 11:55:54.723490 IP6 xxxx:xxxx:830:81::81 > fe80::8e:95ff:fef1:621a: ICMP6, neighbor advertisement, tgt is xxxx:xxxx:830:81::81, length 24 11:55:54.762911 IP6 xxxx:xxxx:830:81::81 > xxxx:xxxx:830:81::82: ICMP6, echo request, id 19484, seq 6, length 64 11:55:54.762931 IP6 xxxx:xxxx:830:81::82 > xxxx:xxxx:830:81::81: ICMP6, echo reply, id 19484, seq 6, length 64 11:55:59.850780 IP6 fe80::1a:44ff:fe65:dbe0 > fe80::8e:95ff:fef1:621a: ICMP6, neighbor solicitation, who has fe80::8e:95ff:fef1:621a, length 32 11:55:59.850817 IP6 fe80::8e:95ff:fef1:621a > fe80::1a:44ff:fe65:dbe0: ICMP6, neighbor advertisement, tgt is fe80::8e:95ff:fef1:621a, length 24 11:56:04.962860 IP6 fe80::8e:95ff:fef1:621a > fe80::1a:44ff:fe65:dbe0: ICMP6, neighbor solicitation, who has fe80::1a:44ff:fe65:dbe0, length 32 11:56:04.963212 IP6 fe80::1a:44ff:fe65:dbe0 > fe80::8e:95ff:fef1:621a: ICMP6, neighbor advertisement, tgt is fe80::1a:44ff:fe65:dbe0, length 24 ________________________________ From: Marco <[email protected]> Sent: Sunday, September 3, 2023 1:32 AM To: [email protected] <[email protected]> Subject: Re: IPv6 Issues with thunderbolt-net driver? Am 02.09.2023 um 22:17:33 Uhr schrieb Alex Balcanquall: > - ping machine 1 IPv6 from machine 2 (this will work) > - try to ssh from machine 1 to machine 2 using IPv6 (this will not > work) Can you run a packet sniffer on both machines to check if the package reaches the interface outgoing and on the other side ingoing?
