Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Tiago Condeixa <tcondeixa@veniamworks.com>
To: wireguard@lists.zx2c4.com
Subject: Wireguard multihomed roaming performance
Date: Fri, 23 Jun 2017 18:04:44 +0100	[thread overview]
Message-ID: <EE8741B3-9787-4522-98B9-D484C4BE7A8E@veniamworks.com> (raw)

Hi Janson,

I have using wireguard in a multihomed scenarios with a board equipped =
with WiFi and LTE.=20
In order to change the interface to be used I just change the route to =
the IP address of the wireguard server, but sometimes it take some time =
to update the endpoint in the server.=20
I was doing a analysis and the problem is not related with wireguard =
server but with the client. Sometimes the client takes a lot of seconds =
to change the IP source address of the wireguard tunnel and it has a =
great impact on handover time.=20
How are you adjusting the IP source address of the tunnel? do you have a =
cache that is periodically update or based on timeout? I have been =
thinking in adding a method for wg(8) that can allow me to change the IP =
source address of the tunnel when I want to roam between =
technologies/interfaces or do you have any better idea?

thank you,
Tiago=

             reply	other threads:[~2017-06-23 16:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23 17:04 Tiago Condeixa [this message]
2017-06-23 17:28 ` Jason A. Donenfeld
2017-06-23 17:47   ` Tiago Condeixa
2017-06-23 18:46     ` Jason A. Donenfeld
2017-06-23 18:57       ` Jason A. Donenfeld
2017-06-23 19:42         ` Jason A. Donenfeld
2017-06-23 20:43           ` Tiago Condeixa
2017-06-26 12:15           ` Tiago Condeixa

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=EE8741B3-9787-4522-98B9-D484C4BE7A8E@veniamworks.com \
    --to=tcondeixa@veniamworks.com \
    --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).