Date: Mon, 21 Jun 2021 08:36:50 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256681 --- Comment #5 from Zhenlei Huang <firstname.lastname@example.org> --- > So in some cases, if the loopback route is disabled and the hardware/logical interface can not forward those packets destined for local, 'No route to host' should be generated. Since release/8.1, a new feature 'IFCAP_LINKSTATE' was introduced, see  and . If an interface have 'IFCAP_LINKSTATE' capability, then the "link" state should be checked before passing those packets to it. I verified this feature on stable/12 and stable/13. The steps: 1. ifconfig vxlan0 create vxlanid 100 vxlanlocal 10.x.x.x vxlanremote 10.y.y.y 2. ifconfig vxlan0 inet 192.0.2.1/24 3. ifconfig vxlan0 inet 192.0.2.2/32 alias 4. netstat -rnWf inet | grep 192.0.2 5. ping -c4 192.0.2.1 6. ping -c4 192.0.2.2 7. route delete 192.0.2.1 8. route delete 192.0.2.2 9. repeat step 4 10. ifconfig vxlan0 down && If create vxlan0 without vxlanid vxlanlocal and vxlanremote, then the link state is not ready. If we delete the loopback route to 192.0.2.1 and 192.0.2.2, ping will response with 'No route to host'. : https://cgit.freebsd.org/src/commit/sys/netinet/ip_output.c?h=stable/8&id=c951da56b4f19a637c7fdf734fc500560a9555de : https://cgit.freebsd.org/src/commit/sys?h=stable/8&id=94190b3925795b145fbd1fbc39df0841ef52f5d5 -- You are receiving this mail because: You are on the CC list for the bug.