From nobody Sat Dec  4 08:59:29 2021
X-Original-To: freebsd-net@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 2C1A118CF05E
	for <freebsd-net@mlmmj.nyi.freebsd.org>; Sat,  4 Dec 2021 08:59:39 +0000 (UTC)
	(envelope-from pi@freebsd.org)
Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(Client did not present a certificate)
	by mx1.freebsd.org (Postfix) with ESMTPS id 4J5kCZ3LBgz3nr4;
	Sat,  4 Dec 2021 08:59:38 +0000 (UTC)
	(envelope-from pi@freebsd.org)
Received: from pi by fc.opsec.eu with local (Exim 4.95 (FreeBSD))
	(envelope-from <pi@freebsd.org>)
	id 1mtQtF-000Hw8-Gp;
	Sat, 04 Dec 2021 09:59:29 +0100
Date: Sat, 4 Dec 2021 09:59:29 +0100
From: Kurt Jaeger <pi@freebsd.org>
To: freebsd-net@freebsd.org
Subject: why multi-hop icmp redirects to 0.0.0.0 on 13.0 ?
Message-ID: <Yast8d1dRd7ZFWr3@fc.opsec.eu>
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-net
List-Help: <mailto:freebsd-net+help@freebsd.org>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Subscribe: <mailto:freebsd-net+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-net+unsubscribe@freebsd.org>
Sender: owner-freebsd-net@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Rspamd-Queue-Id: 4J5kCZ3LBgz3nr4
X-Spamd-Bar: /
Authentication-Results: mx1.freebsd.org;
	dkim=none;
	dmarc=none;
	spf=softfail (mx1.freebsd.org: 2001:14f8:200:4::4 is neither permitted nor denied by domain of pi@freebsd.org) smtp.mailfrom=pi@freebsd.org
X-Spamd-Result: default: False [-0.56 / 15.00];
	 RCVD_TLS_LAST(0.00)[];
	 ARC_NA(0.00)[];
	 RCVD_COUNT_TWO(0.00)[2];
	 FREEFALL_USER(0.00)[pi];
	 FROM_HAS_DN(0.00)[];
	 TO_MATCH_ENVRCPT_ALL(0.00)[];
	 MIME_GOOD(-0.10)[text/plain];
	 TO_DN_NONE(0.00)[];
	 DMARC_NA(0.00)[freebsd.org];
	 R_SPF_SOFTFAIL(0.00)[~all];
	 RCPT_COUNT_ONE(0.00)[1];
	 NEURAL_HAM_MEDIUM(-1.00)[-1.000];
	 NEURAL_HAM_SHORT(-1.00)[-1.000];
	 NEURAL_SPAM_LONG(0.54)[0.540];
	 FROM_EQ_ENVFROM(0.00)[];
	 R_DKIM_NA(0.00)[];
	 MIME_TRACE(0.00)[0:+];
	 ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE];
	 SUBJECT_ENDS_QUESTION(1.00)[];
	 TO_DOM_EQ_FROM_DOM(0.00)[]
X-Spam: Yes
X-ThisMailContainsUnwantedMimeParts: N

Hi!

We (AS12502) recently upgraded one router from 12.2.x to 13.0.x. This
caused some surprising effect, with the router sending out
icmp redirects to 0.0.0.0 over multiple hops:

Example:

inet ------ wan:rtr1:lan ------ rtr2 ------ wan:host
                     x.x.x.1                y.y.y.1

host sends a packet to z.z.z.z and receives an icmp redirect from x.x.x.1
like this:

10:20:16.889185 IP x.x.x..1 > y.y.y.1: ICMP redirect z.z.z.z to host 0.0.0.0, length 48

This has been stopped by net.inet.ip.redirect=0 on rtr1, but my question is:

Why is rtr1 sending those multi-hop icmp redirects at all ?

-- 
pi@FreeBSD.org         +49 171 3101372                  Now what ?