Re: shorewall-nft packages repo

Witold Tosta <[email protected]> Wed, 22 Jul 2026 07:44:18 +0200
Newsgroups gmane.comp.security.shorewall
Message-ID <CANXt+ZZY_+zCH=9LERDahOb+x5qJVNYT1N19XpdGv09J0tCfxQ@mail.gmail.com>
--===============0010171025322086094==
Content-Type: multipart/alternative; boundary="0000000000000ddcf306572ca2d0"

--0000000000000ddcf306572ca2d0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Dave,

Do I need to uninstall the old shorewall and shorewall6 packages first,
leaving only the directories with the configuration files? Can the old
shorewall packages be installed? I'm using Debian Trixie.

Best regards,

Witold Tosta

wt., 21 lip 2026, 08:45 u=C5=BCytkownik Dave Kempe <[email protected]>
napisa=C5=82:

> Hey everyone,
> As a way to get started quickly, I have added shorewall-nft to the Sol1
> packages repo.
> You can set it up here: https://packages.sol1.net/
> and then simply:
> apt install shorewall-nft
> shorewall check
> shorewall migrate
> And you are done.
>
> If encounter any problems with check or migrate, you can back out and go
> back to shorewall, (apt install shorewall etc)
> Note that shorewall-nft conflicts with shorewall and will uninstall it,
> with the migrate command actually flushing iptables rules.
>
> I haven't got any packages repo for rpm based distros, as we are
> debian/ubuntu from way back, but I'm sure a quick rpm command will work t=
he
> same sorta way.
>
> Dave
>
> _______________________________________________
> Shorewall-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/shorewall-users
>

--0000000000000ddcf306572ca2d0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div>Hi Dave,</div><div dir=3D"auto"><br></div><div dir=
=3D"auto">Do I need to uninstall the old shorewall and shorewall6 packages =
first, leaving only the directories with the configuration files? Can the o=
ld shorewall packages be installed? I&#39;m using Debian Trixie.</div><div =
dir=3D"auto"><br></div><div dir=3D"auto">Best regards,</div><div><br></div>=
<div data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><div>Witold Tosta<=
/div></div></div></div><br><div class=3D"gmail_quote gmail_quote_container"=
><div dir=3D"ltr" class=3D"gmail_attr">wt., 21 lip 2026, 08:45 u=C5=BCytkow=
nik Dave Kempe &lt;<a href=3D"mailto:[email protected]">davidkempe@gmail=
.com</a>&gt; napisa=C5=82:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=
=3D"ltr"><div>Hey everyone,</div><div>As a way to get started quickly, I ha=
ve added shorewall-nft to the Sol1 packages repo.</div><div>You can set it =
up here:=C2=A0<a href=3D"https://packages.sol1.net/" target=3D"_blank" rel=
=3D"noreferrer">https://packages.sol1.net/</a></div><div>and then simply:</=
div><div>apt install shorewall-nft</div><div>shorewall check</div><div>shor=
ewall migrate</div><div>And you are done.</div><div><br></div><div>If encou=
nter any problems with check or migrate, you can back out and go back to sh=
orewall, (apt install shorewall etc)</div><div>Note that shorewall-nft conf=
licts with shorewall and will uninstall it, with the migrate command actual=
ly=C2=A0flushing iptables rules.</div><div><br></div><div>I haven&#39;t got=
 any packages repo for rpm based distros, as we are debian/ubuntu from way =
back, but I&#39;m sure a quick rpm command will work the same sorta way.</d=
iv><div><br></div><div>Dave</div><div><br></div></div>
_______________________________________________<br>
Shorewall-users mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank" =
rel=3D"noreferrer">[email protected]</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/shorewall-users" re=
l=3D"noreferrer noreferrer" target=3D"_blank">https://lists.sourceforge.net=
/lists/listinfo/shorewall-users</a><br>
</blockquote></div>

--0000000000000ddcf306572ca2d0--


--===============0010171025322086094==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============0010171025322086094==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline