From: "Alexandru Scvortov" <wireguard@abstractbinary.org>
To: wireguard@lists.zx2c4.com
Subject: What's the purpose of the wg-quick firewall rules?
Date: Mon, 06 Jun 2022 14:32:04 +0100 [thread overview]
Message-ID: <fedd0d21-a55c-4e17-8dcf-dd348e157aee@www.fastmail.com> (raw)
Hi,
I'm trying to understand what the firewall rules that wg-quick adds do.
I see these rules being added:
```
table ip raw {
chain PREROUTING {
type filter hook prerouting priority raw; policy accept;
iifname != "wg0" ip daddr 10.10.1.2 fib saddr type != local counter drop
iifname != "wg0" ip daddr 10.10.0.2 fib saddr type != local counter drop
}
}
table ip mangle {
chain POSTROUTING {
type filter hook postrouting priority mangle; policy accept;
meta l4proto udp mark 0xca6c counter ct mark set mark
}
chain PREROUTING {
type filter hook prerouting priority mangle; policy accept;
meta l4proto udp counter meta mark set ct mark
}
}
```
The `raw` rules seem fine, but I can't figure out what the `mangle` rules are for. They're added in `add_default`, so they have something to do with the "route all traffic through Wireguard" functionality, but removing them doesn't seem to break anything on my laptop.
I think the first iteration of these were added in commit ebcf1ef8b1ad in wireguard-tools, but the commit message is "wg-quick: linux: filter bogus injected packets and don't disable rpfilter", and that doesn't make it any clearer to me.
What breaks if these rules aren't present?
Thank you.
Cheers,
Alex
reply other threads:[~2022-06-27 11:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=fedd0d21-a55c-4e17-8dcf-dd348e157aee@www.fastmail.com \
--to=wireguard@abstractbinary.org \
--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).