From: Arvid Picciani <aep@exys.org>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: will frequently changing allowed-list result in latency spikes?
Date: Wed, 20 Apr 2022 10:05:30 +0200 [thread overview]
Message-ID: <CACD9L=DWEargDr8f1gXzigZ=NQsSz=18vzQMgVQKzUN++r4ELw@mail.gmail.com> (raw)
Hi,
we're currently using wg as point-to-point transport between thousands of vms.
each peer has a separate interface so we can do BGP with bird.
this works extremely well. But due to lack of port-reuse, eventually
you run out of udp ports.
Now i'm thinking of redesigning it with a single wg interface and
using wgs native destination selection which is based on allow-list.
that means every topology change results in a netlink call to wg to
replace all affected peers with a new peer with a new allowed-list.
In a quick test i couldn't see any problems with that. But i'm
worried that might change with scale. Replacing a peer config might
flush its buffer, possibly resulting in packet loss. Or more likely
reset its crypto session, resulting in a latency spike until the
handshake finished.
anyone has more insight into that?
--
+4916093821054
reply other threads:[~2022-04-20 8:05 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='CACD9L=DWEargDr8f1gXzigZ=NQsSz=18vzQMgVQKzUN++r4ELw@mail.gmail.com' \
--to=aep@exys.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).