root@pve1:~# ip -s -s link show en06
PVE1 (sender)
root@pve1:~# ip -s -s link show en06
7: en06: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65520 qdisc pfifo_fast state UP
mode DEFAULT group default qlen 1000
link/ether 02:1a:44:65:db:e0 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
19047333241 20301503 0 0 0 0
RX errors: length crc frame fifo overrun
0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
15558035141 18392655 7 0 0 0
TX errors: aborted fifo window heartbt transns
0 0 0 0 2
PVE2 (destination)
root@pve2:~# ip -s -s link show en05
74: en05: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65520 qdisc pfifo_fast state UP
mode DEFAULT group default qlen 1000
link/ether 02:8e:95:f1:62:1a brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
15561305384 19172991 0 0 0 0
RX errors: length crc frame fifo overrun
0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
19050263184 18347026 0 0 0 0
TX errors: aborted fifo window heartbt transns
0 0 0 0 2
So straight after the PVE1 test i did this.... does this mean they were dropped
before the wire?
root@pve1:~# ssh root@2600:a801:830:81::82
^C
root@pve1:~# ip -s -s link show en06
7: en06: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65520 qdisc pfifo_fast state UP
mode DEFAULT group default qlen 1000
link/ether 02:1a:44:65:db:e0 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
19053852086 20311446 0 0 0 0
RX errors: length crc frame fifo overrun
0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
15565251706 18402383 11 0 0 0
TX errors: aborted fifo window heartbt transns
0 0 0 0 2
________________________________
From: Marco <[email protected]>
Sent: Wednesday, September 6, 2023 5:00 AM
To: [email protected] <[email protected]>
Subject: Re: IPv6 Issues with thunderbolt-net driver?
Am 05.09.2023 um 19:08:28 Uhr schrieb Alex Balcanquall:
> 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...
ip -s -s link show <ifname>
on both machines.
