Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Vicente Bergas <vicencb@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: lost connection on dynamic IP
Date: Tue, 18 May 2021 13:22:31 +0200	[thread overview]
Message-ID: <CAAMcf8BeGzUppFzfc2hF9KvpfU1DfSpncYv4AaK5Qf8_+fC-Rw@mail.gmail.com> (raw)

Hi, i've got the following setup:
A server connected to the Internet through an ISP that provides a
dynamic IP with NAT.
The server keeps the DNS updated with https://github.com/troglobit/inadyn
A client on a tiny embedded board connects to the server by means of
its domain name.
Wireguard configurations are:
# server/etc/wireguard/wg0.conf
[Interface]
ListenPort = port_number
PrivateKey = ...
[Peer]
PublicKey = ...
PresharedKey = ...
PersistentKeepalive = 25
AllowedIPs = 10.0.0.2

# client/etc/wireguard/wg0.conf
[Interface]
PrivateKey = ...
[Peer]
PublicKey = ...
PresharedKey = ...
Endpoint = domain.name.that.resolves.to.a.dynamic.ip:port_number
PersistentKeepalive = 25
AllowedIPs = 10.0.0.1

The server almost never initiates comunications towards the client.
The client sends one packet every minute towards the server.

I think the issue happens when the ISP on the server side shuts down
the Internet connection for more than 1 hour! Then, it is restored
with a new IP.
inadyn detects the new IP and updates the DNS.
At this point the Internet connection is operational again, but the
client remains disconnected until rebooted.

Is this scenario expected to work due to the "Built-in Roaming" ?

Regards,
  Vicenç.

             reply	other threads:[~2021-05-19 18:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 11:22 Vicente Bergas [this message]
2021-05-19 18:43 ` Roman Mamedov
2021-05-19 22:28   ` Vicente Bergas
2021-05-20  6:15     ` Roman Mamedov
2021-05-20 16:20       ` Roman Mamedov
2021-05-20 19:23         ` Max Schulze
2021-05-23 11:44           ` Vicente Bergas

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=CAAMcf8BeGzUppFzfc2hF9KvpfU1DfSpncYv4AaK5Qf8_+fC-Rw@mail.gmail.com \
    --to=vicencb@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).