Development discussion of WireGuard
 help / color / Atom feed
* Android client fails to auto start connection if using a DDNS address as endpoint
@ 2020-04-19 15:21 shadowofdarkness
  2020-05-06 11:01 ` me
  2020-05-06 11:18 ` laszlo.kertesz
  0 siblings, 2 replies; 5+ messages in thread
From: shadowofdarkness @ 2020-04-19 15:21 UTC (permalink / raw)


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.


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

* Android client fails to auto start connection if using a DDNS address as endpoint
  2020-04-19 15:21 Android client fails to auto start connection if using a DDNS address as endpoint shadowofdarkness
@ 2020-05-06 11:01 ` me
  2020-05-06 11:03   ` Jason
  2020-05-06 11:18 ` laszlo.kertesz
  1 sibling, 1 reply; 5+ messages in thread
From: me @ 2020-05-06 11:01 UTC (permalink / raw)




On Apr 19 2020, at 9:01 pm, Dark Shadow <shadowofdarkness at 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.
>

Hm, that's pretty unexpected. Are you using the Go userspace backend or
the kernel module? The settings page will show that at the top if you're
unsure. I've Cc'ed Jason in case this is a problem lower down in the
stack.


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

* Android client fails to auto start connection if using a DDNS address as endpoint
  2020-05-06 11:03   ` Jason
@ 2020-05-06 11:17     ` me
  0 siblings, 0 replies; 5+ messages in thread
From: me @ 2020-05-06 11:17 UTC (permalink / raw)




On May 6 2020, at 4:33 pm, "Jason A. Donenfeld" <Jason at zx2c4.com> wrote:

> Looks like we don't have any retry logic for DNS resolution for the
> case in which there's temporarily no Internet:
> 
> https://git.zx2c4.com/wireguard-android/tree/tunnel/src/main/java/com/wireguard/config/InetEndpoint.java#n91
> 

What do we want to do here, then? Deferring config resolution feels
suboptimal. Deferring tunnel restoration on boot until we have a
connection looks like a semi-reasonable solution.


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

* Android client fails to auto start connection if using a DDNS address as endpoint
  2020-04-19 15:21 Android client fails to auto start connection if using a DDNS address as endpoint shadowofdarkness
  2020-05-06 11:01 ` me
@ 2020-05-06 11:18 ` laszlo.kertesz
  1 sibling, 0 replies; 5+ messages in thread
From: laszlo.kertesz @ 2020-05-06 11:18 UTC (permalink / raw)


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


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

* Android client fails to auto start connection if using a DDNS address as endpoint
  2020-05-06 11:01 ` me
@ 2020-05-06 11:03   ` Jason
  2020-05-06 11:17     ` me
  0 siblings, 1 reply; 5+ messages in thread
From: Jason @ 2020-05-06 11:03 UTC (permalink / raw)


Looks like we don't have any retry logic for DNS resolution for the
case in which there's temporarily no Internet:

https://git.zx2c4.com/wireguard-android/tree/tunnel/src/main/java/com/wireguard/config/InetEndpoint.java#n91


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

end of thread, back to index

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-19 15:21 Android client fails to auto start connection if using a DDNS address as endpoint shadowofdarkness
2020-05-06 11:01 ` me
2020-05-06 11:03   ` Jason
2020-05-06 11:17     ` me
2020-05-06 11:18 ` laszlo.kertesz

Development discussion of WireGuard

Archives are clonable: git clone --mirror http://inbox.vuxu.org/wireguard

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.wireguard


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git