From nobody Sun Jul 31 12:39:36 2022
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 4LwgnD3sYvz4YDlB
	for <freebsd-net@mlmmj.nyi.freebsd.org>; Sun, 31 Jul 2022 12:39:44 +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 4LwgnC4JH5z3cdV
	for <freebsd-net@freebsd.org>; Sun, 31 Jul 2022 12:39:43 +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 1oI8EK-0004yD-PY
	for freebsd-net@freebsd.org;
	Sun, 31 Jul 2022 14:39:36 +0200
Date: Sun, 31 Jul 2022 14:39:36 +0200
From: Kurt Jaeger <pi@freebsd.org>
To: freebsd-net@freebsd.org
Subject: ipfw during 13.0 -> 13.1 fbsd-update - loss of ipv4 connection ?
Message-ID: <YuZ4CNRt6xHICpWt@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: 4LwgnC4JH5z3cdV
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 [-2.10 / 15.00];
	SUBJECT_ENDS_QUESTION(1.00)[];
	NEURAL_HAM_LONG(-1.00)[-1.000];
	NEURAL_HAM_MEDIUM(-1.00)[-1.000];
	NEURAL_HAM_SHORT(-1.00)[-1.000];
	MIME_GOOD(-0.10)[text/plain];
	RCVD_TLS_LAST(0.00)[];
	MLMMJ_DEST(0.00)[freebsd-net@freebsd.org];
	R_DKIM_NA(0.00)[];
	FROM_EQ_ENVFROM(0.00)[];
	ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE];
	MIME_TRACE(0.00)[0:+];
	RCPT_COUNT_ONE(0.00)[1];
	R_SPF_SOFTFAIL(0.00)[~all];
	TO_DN_NONE(0.00)[];
	RCVD_COUNT_TWO(0.00)[2];
	ARC_NA(0.00)[];
	DMARC_NA(0.00)[freebsd.org];
	FREEFALL_USER(0.00)[pi];
	TO_MATCH_ENVRCPT_ALL(0.00)[];
	FROM_HAS_DN(0.00)[];
	TO_DOM_EQ_FROM_DOM(0.00)[]
X-ThisMailContainsUnwantedMimeParts: N

Hello,

see also: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265532

I had several cases where an freebsd-upgrade from 13.0 -> 13.1 with an
active ipfw ruleset:

# firewall, ipfw based
firewall_enable="YES"
firewall_type="OPEN"

caused the host after reboot to loose ipv4 connectivity due to
ipfw blocks.

Has anyone else seen this ?

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