From: Allen Chen <firstname.lastname@example.org>
Subject: Re: Best strategy for multiple point-to-point tunnels
Date: Tue, 6 Apr 2021 16:28:29 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
The process of update is bugging me a lot. Does a update break the 1-n
connection? There should be a way to check the version compatibility.
But I don't know how.
On 3/30/2021 7:55 AM, Chriztoffer Hansen wrote:
> On Tue, 30 Mar 2021 at 13:53, Chriztoffer Hansen wrote:
>> On Thu, 25 Mar 2021 at 23:35, Karol Babioch wrote:
>>> What is your recommendation on handling multiple peer-to-peer tunnels?
>>> Should I go for multiple interfaces or for one interface with multiple
>> If you plan to do L3 routing over the P2P tunnels (e.g.
>> OSPF/BGP/EIGRP/Babel/etc.). A dedicated wg interface per remote
>> endpoint is generally recommended.
> If you are doing a road-warrior style set-up. One WG interface (e.g.
> per subnet for road-warrior groups) at your aggregation point/server
> will be enough.
next prev parent reply other threads:[~2021-04-06 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 22:35 Best strategy for multiple point-to-point tunnels Karol Babioch
2021-03-30 11:53 ` Chriztoffer Hansen
2021-03-30 11:55 ` Chriztoffer Hansen
2021-04-06 20:28 ` Allen Chen [this message]
2021-04-07 11:16 ` Karol Babioch
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).