From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Reid Rankin <reidrankin@gmail.com>
Cc: Daniel Golle <daniel@makrotopia.org>,
Florent Daigniere <nextgens@freenetproject.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: passing-through TOS/DSCP marking
Date: Thu, 17 Jun 2021 22:54:55 +0200 [thread overview]
Message-ID: <87lf78dxeo.fsf@toke.dk> (raw)
In-Reply-To: <CAMaqUZ09KRtp01OK3u-Di52X_kH9eT4E-wmnPc6QzjSCd5dEiw@mail.gmail.com>
Reid Rankin <reidrankin@gmail.com> writes:
> It can also be done in a shell script with nftables (maybe iptables too,
> haven't tried) by taking advantage of fwmark passthrough. You can have one
> rule that matches incoming outgoing packets (heh) with a certain dscp value
> and marks them, and another rule that matches outgoing outgoing packets
> with that mark and sets the DSCP bits back.
The fwmark is not passed through wireguard, though, it's cleared during
skb scrubbing:
https://elixir.bootlin.com/linux/latest/source/net/core/skbuff.c#L5344
There's an fwmark config that you can set which will make wireguard
apply a certain mark to all outgoing packets, but that has nothing to
do with what was set on the inner packet...
-Toke
next prev parent reply other threads:[~2021-06-17 20:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 13:24 passing-through TOS/DSCP marking Daniel Golle
2021-06-16 16:28 ` Jason A. Donenfeld
2021-06-16 19:26 ` Daniel Golle
2021-06-16 23:33 ` Toke Høiland-Jørgensen
2021-06-17 7:55 ` Florent Daigniere
2021-06-17 9:41 ` Daniel Golle
2021-06-17 12:24 ` Toke Høiland-Jørgensen
[not found] ` <CAMaqUZ09KRtp01OK3u-Di52X_kH9eT4E-wmnPc6QzjSCd5dEiw@mail.gmail.com>
2021-06-17 20:54 ` Toke Høiland-Jørgensen [this message]
2021-06-17 23:04 ` Toke Høiland-Jørgensen
2021-06-18 12:24 ` Jason A. Donenfeld
2021-06-21 12:36 ` Daniel Golle
2021-06-21 14:27 ` Toke Høiland-Jørgensen
2021-06-30 17:23 ` Daniel Golle
2021-06-30 20:55 ` Toke Høiland-Jørgensen
2021-07-04 14:15 ` Daniel Golle
2021-07-05 15:21 ` Toke Høiland-Jørgensen
2021-07-05 16:05 ` Daniel Golle
2021-07-05 16:59 ` Toke Høiland-Jørgensen
2021-07-05 17:26 ` Daniel Golle
2021-07-05 21:20 ` Toke Høiland-Jørgensen
2021-07-06 7:00 ` Florent Daigniere
2021-07-06 20:08 ` Luiz Angelo Daros de Luca
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=87lf78dxeo.fsf@toke.dk \
--to=toke@toke.dk \
--cc=Jason@zx2c4.com \
--cc=daniel@makrotopia.org \
--cc=nextgens@freenetproject.org \
--cc=reidrankin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.