Re: Introducing shorewall-nft

--===============8523967632044057279==
Content-Type: multipart/alternative; boundary="00000000000009a5ba0656f450ec"

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

This would be a neat FR Erich.
I'm sure we can do something like that, nft is basically json once
compiled. Happy to discuss it in a GitHub issue, so we can model it out and
get my team involved.

Dave

On Sun, 19 July 2026, 8:23=E2=80=AFpm Erich Titl, <[email protected]> wro=
te:

> So we might need to have a
> shorewall-nft compiler on separate hardware.
>
>
>

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

<div dir=3D"auto"><div>This would be a neat FR Erich.</div><div dir=3D"auto=
">I&#39;m sure we can do something like that, nft is basically json once co=
mpiled. Happy to discuss it in a GitHub issue, so we can model it out and g=
et my team involved.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Dav=
e<br><br><div class=3D"gmail_quote gmail_quote_container" dir=3D"auto"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Sun, 19 July 2026, 8:23=E2=80=AFpm Eri=
ch Titl, &lt;<a href=3D"mailto:[email protected]">[email protected]</a>=
&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">So we might need to hav=
e a <br>
shorewall-nft compiler on separate hardware.<br>
<br><br></blockquote></div></div></div>

--00000000000009a5ba0656f450ec--


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


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