Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Laszlo KERTESZ <laszlo.kertesz@gmail.com>
To: Dark Shadow <shadowofdarkness@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Android client fails to auto start connection if using a DDNS address as endpoint
Date: Wed, 6 May 2020 14:18:51 +0300	[thread overview]
Message-ID: <CANcuY=qdMqMtCd=-8M5zYU=fRokkWokMa9dDJwUBHh5=M=nj6Q@mail.gmail.com> (raw)
In-Reply-To: <CAMXzSMozuS_dSpODmp3LzAmoetr9jKXUZpbQthx5P9YXk-xGAw@mail.gmail.com>

Hi,
I too have this issue. My ISP does not provide a fixed IP address and
if the address changes, the Android client does not reconnect. Not
very user friendly as it is hard to do external checks and restart on
mobile.
Also this is true for the desktop version of wireguard, at least on
Linux with both ifupdown and systemd-networkd (i could script a check
and restart easily though).


On Wed, May 6, 2020 at 1:49 PM Dark Shadow <shadowofdarkness@gmail.com> wrote:
>
> I set up Wireguard and had it working fine when manually starting the
> connection.
> After that I wanted to have it be always on so that it would auto
> connect when turning the phone on but I found that it would say it was
> connected but no data would transfer.
> Manually turning it off and on again would fix the connection
>
> If I change the server address to a IP address everything works
> correctly and the connection just works after turning on the phone.
>
> I assume this is a bug that can hopefully be fixed as I would prefer
> to use the dyndns address in the settings.

      parent reply	other threads:[~2020-05-06 11:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-19 15:31 Dark Shadow
2020-05-06 11:01 ` Harsh Shandilya
2020-05-06 11:03   ` Jason A. Donenfeld
2020-05-06 11:17     ` Harsh Shandilya
2020-05-06 11:18 ` Laszlo KERTESZ [this message]

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='CANcuY=qdMqMtCd=-8M5zYU=fRokkWokMa9dDJwUBHh5=M=nj6Q@mail.gmail.com' \
    --to=laszlo.kertesz@gmail.com \
    --cc=shadowofdarkness@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).