Alexander Bluhm <bl...@openbsd.org> writes: > On Sat, Sep 07, 2024 at 01:38:08PM +0300, Alexander Shursha wrote: >> I was wrong, TSO has no effect. > > Good. Then this report makes more sense. > >> ping6 2a09:5302:ffff::1 >> PING 2a09:5302:ffff::1 (2a09:5302:ffff::1): 56 data bytes >> ^C >> --- 2a09:5302:ffff::1 ping statistics --- >> 4 packets transmitted, 0 packets received, 100.0% packet loss >> >> ndp -an >> Neighbor Linklayer Address Netif Expire >> S Flags >> 2a09:5302:ffff::1 (incomplete) vio0 1s >> I 2 >> 2a09:5302:ffff::1c68 52:54:00:f1:31:af vio0 permanent >> R l >> fe80::5054:ff:fef1:31af%vio0 52:54:00:f1:31:af vio0 permanent >> R l > > Usually with such bugs I turn off pf. Maybe it blocks some ICMPv6. > Does it work after pfctl -d ? I disabled the pf, ping did not appear.
> > Then do some tcpdump to see if neigbor discovery packets go in or > out. tcpdump -i pflog0 may also help debugging. tcpdump -ni vio0 host fe80::5054:ff:fecd:f988 tcpdump: listening on vio0, link-type EN10MB 15:17:50.724847 fe80::5054:ff:fecd:f988 > ff02::1:ff00:1: icmp6: neighbor sol: who has 2a04:5201:2::1 15:17:51.724837 fe80::5054:ff:fecd:f988 > ff02::1:ff00:1: icmp6: neighbor sol: who has 2a04:5201:2::1 15:17:53.714947 fe80::5054:ff:fecd:f988 > ff02::1:ff00:1: icmp6: neighbor sol: who has 2a04:5201:2::1 tcpdump -i pflog0 tcpdump: WARNING: snaplen raised from 116 to 160 tcpdump: listening on pflog0, link-type PFLOG ^C 0 packets received by filter 0 packets dropped by kernel -- Alexander Shursha
