From: "b13253@gmail.com" <b13253@gmail.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: wg-quick nft instead of iptables
Date: Mon, 9 Dec 2019 20:28:50 +0800 [thread overview]
Message-ID: <CA+7UkwLFoXc5SuhC9hCd=gWT1vbOk-Jd_WEe119trErJ+v=FiQ@mail.gmail.com> (raw)
In-Reply-To: <87zhg3ymwi.fsf@thalheim.io>
nft is a replacement for iptables, and some distributions (e.g.
Debian) prefer using nft since it is more capable and advanced.
I think it is important to use nft first if it is installed on the
system, then fallback to iptables; rather than in the opposite order.
I suggest that it is better to modify the patch to support iptables
just in case nft is not pre-installed on some distros.
Best regards
On Mon, Dec 9, 2019 at 6:59 PM Jörg Thalheim <joerg@thalheim.io> wrote:
>
>
> Have you tried if iptables-nftables-compat (might have different names,
> depending distribution) works for the rules used in wg-quick?
> Its a wrapper that translate iptables rules to nft transparently
> by providing a iptables executable.
>
>
> Julian Wollrath <jwollrath@web.de> writes:
>
> > Hi,
> >
> > with the newest snapshot wg-quick unfortunately requires iptables while
> > I only have nftables installed. The attached diff handles the rules
> > with nftables instead, maybe somebody finds it useful. The small caveat
> > is, that the rule deletion might not work for everyone.
> >
> >
> > Cheers,
> > Julian
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-12-09 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 15:51 Julian Wollrath
2019-12-08 13:20 ` Jörg Thalheim
2019-12-09 12:28 ` b13253 [this message]
2019-12-09 15:51 ` Daniel Kahn Gillmor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+7UkwLFoXc5SuhC9hCd=gWT1vbOk-Jd_WEe119trErJ+v=FiQ@mail.gmail.com' \
--to=b13253@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).