Date: Tue, 14 Aug 2018 04:56:23 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 221137] FreeBSD 11+ does not send ICMP redirects Message-ID: <bug-221137-7501-tkZrRxGyY1@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221137-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-221137-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=3D221137 Stephen McKay <mckay@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mckay@FreeBSD.org --- Comment #8 from Stephen McKay <mckay@FreeBSD.org> --- Created attachment 196187 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D196187&action= =3Dedit Plausible icmp redirect fix for ipv4 and ipv6 I'm surprised that this bug is still unfixed after a year and quite surpris= ed that it is marked "Affects Only Me". ICMP redirects are still in all the R= FCs and are not deprecated, so FreeBSD's recent inability to generate them affe= cts everyone who wishes to be RFC compliant. I have attached a plausible minimalist fix. When net.inet.ip.redirect is s= et (net.inet6.ip6.redirect for ipv6) fast path forwarding (which lacks redirect generation ability) is not attempted. This means the standard code is used= and ICMP redirects are generated. Anyone wishing to have fast path forwarding at the cost of never generating ICMP redirects can disable redirects using sysctl. This might be considered a strong position to take, but the alternative (ignoring an obvious bug) seems to me to be a stronger position with no up side. I think this issue should be resolved before 12 ships. Please let your thoughts be known. --=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-221137-7501-tkZrRxGyY1>