wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Karol Babioch <karol@babioch.de>
To: wireguard@lists.zx2c4.com
Subject: Re: Best strategy for multiple point-to-point tunnels
Date: Wed, 7 Apr 2021 13:16:02 +0200	[thread overview]
Message-ID: <cd76a8a1-f09d-77c1-0284-b7d449cd2cd7@babioch.de> (raw)
In-Reply-To: <76daec03-67b8-25a7-a2c1-bd51a0e9c891@harbourfrontcentre.com>


Am 06.04.21 um 22:28 schrieb Allen Chen:
> 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.

right now there are no incompabilities (AFAIK). Not sure how this will
be handled in the future. I guess only time will tell.

I was hoping that some (core) developer could share his thoughts on what
it could look like, but maybe its also too theoretical and can only be
answered, once there is an issue and we know what is affected, etc.

Best regards,
Karol Babioch

      reply	other threads:[~2021-04-07 11:16 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
2021-04-07 11:16       ` Karol Babioch [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 \
    --in-reply-to=cd76a8a1-f09d-77c1-0284-b7d449cd2cd7@babioch.de \
    --to=karol@babioch.de \
    --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).