Development discussion of WireGuard
 help / color / mirror / Atom feed
* Wireguard multihomed roaming performance
@ 2017-06-23 17:04 Tiago Condeixa
  2017-06-23 17:28 ` Jason A. Donenfeld
  0 siblings, 1 reply; 8+ messages in thread
From: Tiago Condeixa @ 2017-06-23 17:04 UTC (permalink / raw)
  To: wireguard

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=

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2017-06-26 11:59 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-06-23 17:04 Wireguard multihomed roaming performance Tiago Condeixa
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

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