Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Jordan Glover <Golden_Miller83@protonmail.ch>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "jwollrath@web.de" <jwollrath@web.de>,
	"wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH] wg-quick: linux: add support for nft and prefer it
Date: Tue, 10 Dec 2019 17:05:44 +0000	[thread overview]
Message-ID: <G4y-P2Nndjy1FeZWH6oDZqfhtvl23C4Ezs4x1oZIpieVeppTVu15YYim4wvpIo7LQJrVgmTV8IjnGCKScyTAGUjheEol0zr0n-pot3AJKik=@protonmail.ch> (raw)
In-Reply-To: <CAHmME9pdqq23OXNPHLT-YyXCKTVTKJNyfz9D+Q0jADAN=BDhnA@mail.gmail.com>

On Tuesday, December 10, 2019 4:54 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> On Tue, Dec 10, 2019 at 5:52 PM Jordan Glover
> Golden_Miller83@protonmail.ch wrote:
>
> > On Tuesday, December 10, 2019 3:48 PM, Jason A. Donenfeld Jason@zx2c4.com wrote:
> >
> > > If nft(8) is installed, use it. These rules should be identical to the
> > > iptables-restore(8) ones, with the advantage that cleanup is easy
> > > because we use custom table names.
> >
> > I wonder if nft should be used only if iptables isn't installed instead.
> > Nowadays iptables has nft backend which I believe is default and will
> > translate iptables rules to nft automatically. On my system iptables rules
> > from wg-quck are already shown in "nft list ruleset".
> > I'm not sure if this work in reverse - are nft rules automatically translated
> > to iptables and shown in iptables-save? If not then using iptables of available
> > seems more versatile for the job.
>
> iptables rules and nftables rules can co-exist just fine, without any
> translation needed. Indeed if your iptables is symlinked to
> iptables-nft, then you'll insert nftables rules when you try to insert
> iptables rules, but it really doesn't matter much either way (AFAIK).
> I figured I'd prefer nftables over iptables if available because I
> presume, without any metrics, that nftables is probably faster and
> slicker or something.

As I said before, my concern is more about people being fully aware of state
of their firewall rather than if it technically works.

Jordan
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2019-12-10 17:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10 15:48 Jason A. Donenfeld
2019-12-10 16:52 ` Jordan Glover
2019-12-10 16:54   ` Jason A. Donenfeld
2019-12-10 17:05     ` Jordan Glover [this message]
2019-12-10 17:11       ` Jason A. Donenfeld
2019-12-10 17:12     ` Roman Mamedov
2019-12-10 17:28       ` Davide Depau
2019-12-10 17:33       ` Matthias Urlichs
2019-12-10 17:36       ` Jason A. Donenfeld
2019-12-10 18:00         ` Roman Mamedov
2019-12-10 18:58         ` Jordan Glover
2019-12-10 19:15           ` Jason A. Donenfeld
2019-12-10 20:30             ` Jordan Glover
2019-12-10 20:34               ` Jason A. Donenfeld
2019-12-10 21:56       ` Vasili Pupkin
2019-12-10 22:09         ` Jason A. Donenfeld
2019-12-10 22:27           ` Vasili Pupkin
2019-12-12 11:21             ` Jason A. Donenfeld
2019-12-10 17:31 ` Vasili Pupkin
2019-12-10 17:38   ` Jason A. Donenfeld

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='G4y-P2Nndjy1FeZWH6oDZqfhtvl23C4Ezs4x1oZIpieVeppTVu15YYim4wvpIo7LQJrVgmTV8IjnGCKScyTAGUjheEol0zr0n-pot3AJKik=@protonmail.ch' \
    --to=golden_miller83@protonmail.ch \
    --cc=Jason@zx2c4.com \
    --cc=jwollrath@web.de \
    --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).