wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: daniel@dumke.me
Cc: wireguard <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard massive amount data
Date: Thu, 23 Sep 2021 10:00:19 -0600	[thread overview]
Message-ID: <CAHmME9puBnmEYfsGqf4ReshhoSHTE5tv7sEVW7MSpuWpS-fr=Q@mail.gmail.com> (raw)
In-Reply-To: <EBVVZQ.U9BF94AEV1NE@dumke.me>

Sounds likely to be a routing loop? I'm not sure whether NM sets up
policy routing to avoid this like wg-quick(8) does. I would hope they
do, but it might also be rather lazy and not. Worth looking into, I
suppose. In the interim, wg-quick will probably do the right thing.

  reply	other threads:[~2021-09-23 16:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23 10:47 Wireguard massive amount data Daniel Dumke
2021-09-23 16:00 ` Jason A. Donenfeld [this message]
2021-09-24 10:23 ` nekochan

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 \
    --in-reply-to='CAHmME9puBnmEYfsGqf4ReshhoSHTE5tv7sEVW7MSpuWpS-fr=Q@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=daniel@dumke.me \
    --cc=wireguard@lists.zx2c4.com \


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