Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Cong Wang <>
To: "Jason A. Donenfeld" <>
Cc: Netdev <>,
	 WireGuard mailing list <>,
	Cong Wang <>,
	Peilin Ye <>
Subject: Re: [Patch net] wireguard: preserve skb->mark on ingress side
Date: Thu, 7 Oct 2021 13:55:54 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi, Jason

On Mon, Sep 27, 2021 at 8:27 PM Cong Wang <> wrote:
> On Mon, Sep 27, 2021 at 8:22 PM Jason A. Donenfeld <> wrote:
> >
> > Hi Cong,
> >
> > I'm not so sure this makes sense, as the inner packet is in fact
> > totally different. If you want to distinguish the ingress interface,
> The contents are definitely different, but skb itself is the same.
> Please also take a look at other tunnels, they all preserve this
> in similar ways, that is, comparing net namespaces. Any reason
> why wireguard is so different from other tunnels?

Any response?


      reply	other threads:[~2021-10-07 20:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28  3:19 Cong Wang
2021-09-28  3:22 ` Jason A. Donenfeld
2021-09-28  3:27   ` Cong Wang
2021-10-07 20:55     ` Cong Wang [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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).