On Jun 16, 2022, at 19:05, Andrew Cagney wrote:
>
>
>>
>> I think the entire command can go. We mostly rewrote the tests but would
>> still need to fix up more tests to do this.
>
> As in the <> command, or just <> within?
>
> Tests do need an OS neutral way to dump kernel state/policy, but
On Thu, 16 Jun 2022 at 12:12, Paul Wouters wrote:
>
>
>
> > On Jun 16, 2022, at 11:56, Antony Antony wrote:
> >
> > I made iptables optional now. this will allow
>
> Thanks!
>
> > do we need iptables in "ipsec look" To me it seems a remenant from KLIPS
> > mast?
>
> I think the entire command ca
> On Jun 16, 2022, at 11:56, Antony Antony wrote:
>
> I made iptables optional now. this will allow
Thanks!
> do we need iptables in "ipsec look" To me it seems a remenant from KLIPS
> mast?
I think the entire command can go. We mostly rewrote the tests but would still
need to fix up more
I made iptables optional now. this will allow adding nftables soon.
CAT and NFLOG are optional now, ATM need iptabels. I don't know the syntax
for nft yet.
Also the use of iptbales in "ipsec verify" is optional
do we need iptables in "ipsec look" To me it seems a remenant from KLIPS
mast?
the
Breaking down task of adding nft support.
On Wed, Jun 08, 2022 at 10:38:16AM -0400, Andrew Cagney wrote:
> this week it is https://github.com/libreswan/libreswan/issues/116
I am in favor of adding nft support along with iptable support. Add build
variable? Any thoughts on how to add nft support
