Date: Sat, 3 Jan 2026 13:51:03 +0900
From: Dominique Martinet <asmadeus@codewreck.org>
To: "W. Michael Petullo" <mike@flyn.org>
Cc: ~alpine/devel@lists.alpinelinux.org
Subject: Re: Preferred firewall
Message-ID: <aVigNx0R5idi1JkJ@codewreck.org>
References: <aVhxrpww1wvEmBWB@imp.flyn.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <aVhxrpww1wvEmBWB@imp.flyn.org>

W. Michael Petullo wrote on Fri, Jan 02, 2026 at 07:32:30PM -0600:
> I maintain an application on Alpine, and I have become a little confused
> about the distribution's preferred firewall stack. Until now, I have
> used awall. Recently, I found that my approach had to change slightly,
> because Alpine 3.23 does not by default provide the ip_tables module:

FWIW alpine 3.19 changed the default iptables package from
iptables-legacy to iptables-nft, so iptables commands (and thus as far
as I understand awall as well, although I didn't check) should not use
the ip_tables module, but nftables

If you still pull in iptables-legacy try using iptables-nft from the
iptables package

-- 
Dominique Martinet | Asmadeus