https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284606
--- Comment #28 from [email protected] --- (In reply to commit-hook from comment #25) by the way - I've found a way to reproduce the issue - fastopen is the way: on server VM (vtnet0 172.22.7.15/24): setup script (run in bash): ifconfig wg create name wg0 192.168.1.1/24 up wg set wg0 private-key <(echo "6G0V1B5MxxN8vBh3STwTmXIe/lelKL9mH6MgSoEAW3U=") \ listen-port 55555 peer obKySGvy/PhXVXTd8qmlVE8AIBvvMw9xHm778OG2QE0= \ allowed-ips 192.168.1.2/32 ifconfig lo1 create 192.168.1.11/32 up sysctl net.inet.ip.forwarding=1 sysctl net.inet.tcp.fastopen.server_enable=1 kldload ipfw kldload ipfw_pmod ipfw add tcp-setmss 1000 tcp from any to any via wg0 tcpflags syn ipfw add pass ip from any to any fetch https://people.freebsd.org/~pkelsey/tfo-tools/tfo-srv.c cc -o tfo-srv tfo-srv.c ./tfo-srv ------ on client VM (vtnet0 172.22.7.14/24): setup script (run in bash): ifconfig wg create name wg0 192.168.1.2/24 up wg set wg0 private-key <(echo "gCWPuTVuD2+YBkz3OnQycmq78KpnjVbyBOiEBpBEQXE=") \ peer oN8c0McyLVdBm/+u6jJAEUU71pOo4hHrnmDjlS+IaSs= \ allowed-ips 192.168.1.9/24 endpoint 172.22.7.15:55555 ping -c1 192.168.1.1 ifconfig lo1 create 172.22.1.12/32 up fetch https://people.freebsd.org/~pkelsey/tfo-tools/tfo-client.c cc -o tfo-client tfo-client.c --- trigger panic --- ./tfo-client -r 1000 -s 1000 192.168.1.11 22222 # that run ok ./tfo-client -r 1000 -s 1000 192.168.1.11 22222 # that panics on server ----- VMs should be able to reach each other, patch clearly prevents panic Kyle, thanks a lot -- You are receiving this mail because: You are on the CC list for the bug.
