Date: Thu, 04 Jul 2024 22:23:16 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 280132] EHOSTUNREACH when using IPv4 over IPv6 nexthop Message-ID: <bug-280132-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D280132 Bug ID: 280132 Summary: EHOSTUNREACH when using IPv4 over IPv6 nexthop Product: Base System Version: 14.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: email@luiz.eng.br After upgrading one of my hosts from FreeBSD 13.2-RELEASE to 14.1-RELEASE, I started running into issues when originating IPv4 traffic from the host.=20 On my public interface, I have a single IPv6 GUA address. No IPv4.=20 I have a loopback interface that has a public IPv4 address configured on it, with a /32 netmask.=20 I then install an IPv4 default route with: route add -net default -inet6 2a12:6e40:0::xx This setup works fine on the 13.2 host, but on the 14.1 host, it results in= a EHOSTUNREACH. I first noticed the issue because unbound was having issues w= ith domains that had only IPv4 nameservers, but I was also able to reproduce it when originating any type of IPv4 traffic from the host: mtr, telnet, ping = all fail.=20 I compared the netstat -no4 and netstat -nr4 outputs between the two systems and they are similar, changing only the last octet of the IPs between the systems.=20 I don't have a lot of experience with dtrace, but I put together a small sc= ript to check the nhop_object returned by fib4_lookup and I noticed that on Free= BSD 14.1 nh_ifa has an IPv6 link-local address, while on 13.2 it has an IPv4 (w= hich interestingly is not the public one). I'm glad to provide more information and run more tests on request. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-280132-227>