From: Thomas Woyzek <iddqd.x84@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: reconnecting client (LTE) with dynamic IPv4
Date: Fri, 3 Aug 2018 12:41:35 +0200 [thread overview]
Message-ID: <CAKg0LU=6BAj17882is6t85b4F+S80KAOnm6Bm0p34CaofXJUUw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 582 bytes --]
Hi
I'm trying to run wireguard on an embedded linux device instead of openvpn.
Everything is going as planned, until the client receives a new IP from the
mobile provider (LTE, ipv4), e.g. after a reconnect.
The endpoint, debian router behind nat does not recognize the new IP from
the embedded device. And the "last handashake" is just keep going. Sometimes
it works, but mostly not.
The embedded device use libqmi but over ethernet is the same issue.
Only a restart of the WG interface on the router brings the connection up
again.
What am I doing wrong?
Best regards,
TOM
[-- Attachment #2: Type: text/html, Size: 2565 bytes --]
reply other threads:[~2018-08-03 10:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAKg0LU=6BAj17882is6t85b4F+S80KAOnm6Bm0p34CaofXJUUw@mail.gmail.com' \
--to=iddqd.x84@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).