Date: Sat, 15 Mar 2025 07:49:49 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 285422] IPv4 source address selection is broken (with loopbacks) Message-ID: <bug-285422-7501-vsHgF642uc@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-285422-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-285422-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285422 Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zarychtam@plan-b.pwste.edu. | |pl --- Comment #1 from Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> --- (In reply to Lexi Winter from comment #0) I don't know if this is a bug or not, but this is how it has been since the beginning when in FreeBSD was introduced the ability to send IPv4 packets via IPv6 next-hops. In RFC 5735 we can read: 0.0.0.0/8 - Addresses in this block refer to source hosts on "this" network. Address 0.0.0.0/32 may be used as a source address for this host on this network; other addresses within 0.0.0.0/8 may be used to refer to specified hosts on this network ([RFC1122], Section 3.2.1.3). Why do you think that address 0.0.0.0 is the wrong one? You can still use the loopback address as the source for ping here: # ping 2.2.2.2 -S 1.1.1.1 -- 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-285422-7501-vsHgF642uc>