Hi list,
Doing tcpdump(8) on a wireguard tunnel yields:
--------------------------------------------------------------------------------
# tcpdump -n -i tun0 icmp6
tcpdump: listening on tun0, link-type LOOP
18:44:34.742106 2001:470:7653:5::11 > 2001:638:60f:110::1:2: icmp6: echo
request [flowlabel 0xb6f77]
18:44:34.754246 bad-ip-version 6
18:44:35.802498 2001:470:7653:5::11 > 2001:638:60f:110::1:2: icmp6: echo
request [flowlabel 0xb6f77]
18:44:35.814841 bad-ip-version 6
18:44:36.860380 2001:470:7653:5::11 > 2001:638:60f:110::1:2: icmp6: echo
request [flowlabel 0xb6f77]
18:44:36.872536 bad-ip-version 6
18:44:37.917605 2001:470:7653:5::11 > 2001:638:60f:110::1:2: icmp6: echo
request [flowlabel 0xb6f77]
18:44:37.929694 bad-ip-version 6
—————————————————————————————————————————
Huh? I thought that 6 is the current version? ;-)
Also, the echo replies are not shown, although I know they exist. Is there a
known problem with tcpdump(8) on wireguard tunnels?
# uname -a
OpenBSD wg.rebehn.net 6.5 GENERIC#2 amd64
dmesg|grep GENERIC
OpenBSD 6.5-current (GENERIC) #2: Sun Jun 2 00:21:42 MDT 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
Running under VMware ESXI 6.7
Manpage and mailing list did not give any hints.
Cheers,
Heinrich
