Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Glen Bojsza <gbojsza@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Wireguard client not roaming
Date: Sat, 5 May 2018 18:34:27 -0400	[thread overview]
Message-ID: <CACW8NbAnCtceEQLqgJ6vaCHexH3dH_uq82TTPuYKeb-C55NM-Q@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]

Hello,

I have two open-wrt routers running wireguard.

B1300 wireguard Client and B1300 wireguard server.

I leave the B1300 wireguard server at the main location and take the B1300
wireguard client to different locations for testing speeds against
different ISPs.

The B1300 wireguard client fails to connect when moved from site to site
unless the B1300 wireguard server is rebooted?

To get the testing I need done for speeds I had to have someone reboot the
B1300 wireguard server...once it came up the B1300 wireguard client would
connect without any other issues and I did my testing (side note - the
speeds tested showed excellent speeds compared to my OpenVPN server back at
the main location).

There must be a configuration parameter that tells the wireguard server to
look for a new connection on wg0 interface ...I am guessing that the keep
alive timer (set for 25 seconds) locks the wg0 interface up...or not.

I am hoping for any advice that can help me to fix this issue given I have
a long trip coming up in a few weeks and I would prefer wireguard to
OpenVPN given it's speed.

thanks.

[-- Attachment #2: Type: text/html, Size: 1322 bytes --]

             reply	other threads:[~2018-05-05 22:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-05 22:34 Glen Bojsza [this message]
2018-05-06  1:02 ` Jason A. Donenfeld
2018-05-29  5:35 ` Recommended Mini-VM image? John Huttley
2018-05-29  9:25   ` Markus Lindenberg
2018-05-29 14:11   ` Ryan Whelan

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=CACW8NbAnCtceEQLqgJ6vaCHexH3dH_uq82TTPuYKeb-C55NM-Q@mail.gmail.com \
    --to=gbojsza@gmail.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).