From: tomt@adslweb.co.uk
To: wireguard@lists.zx2c4.com
Subject: Android Client Won't Disconnect Tunnel
Date: Wed, 05 May 2021 08:47:26 +0100 [thread overview]
Message-ID: <f4166ec7d77fa22bdd727edafe9c58ad@adslweb.co.uk> (raw)
Hi,
I've installed WireGuard for Android v1.0.20210211 ( Go userspace
backend v0.0.20201118 ) on to my Huawei P30 running Android 10 and my
Lenovo Tab4 8Plus running Lineage OS Android 10
Both clients can connect to my OPNsense firewall via WireGuard and
traffic routes as expected. OPNsense shows the connection in List
Configuration and Handshake. When the VPN is active the 'key' is shown
in the status bar and all is working fine.
When I disable the client using the slider the 'key' disappears from the
statue bar, but OPNsense still shows the connection as active and data
can still route from the phone or tablet via the VPN, even though I've
disabled it.
If I check the client log, they both contain entries similar to the
following:
05-05 08:32:08.180 31602 31629 I WireGuard/GoBackend: Bringing tunnel
RemoteAccesss DOWN
05-05 08:32:08.181 31602 31629 D WireGuard/GoBackend/RemoteAccesss:
Device closing
05-05 08:32:08.182 31602 32422 D WireGuard/GoBackend/RemoteAccesss:
Routine: event worker - stopped
05-05 08:32:08.186 31602 31602 E WireGuard/ObservableTunnel:
java.lang.NullPointerException: Attempt to invoke virtual method
'java.lang.String[] java.lang.String.split(java.lang.String)' on a null
object reference
05-05 08:32:08.186 31602 31602 E WireGuard/ObservableTunnel: at
com.wireguard.android.backend.GoBackend.getStatistics(GoBackend.java:4)
05-05 08:32:08.186 31602 31602 E WireGuard/ObservableTunnel: at
com.wireguard.android.model.TunnelManager$getTunnelStatistics$2$1.invokeSuspend(TunnelManager.kt:5)
05-05 08:32:08.186 31602 31602 E WireGuard/ObservableTunnel: at
kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:3)
05-05 08:32:08.186 31602 31602 E WireGuard/ObservableTunnel: at
kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:15)
05-05 08:32:08.186 31602 31602 E WireGuard/ObservableTunnel: at
kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:1)
05-05 08:32:08.186 31602 31602 E WireGuard/ObservableTunnel: at
kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:11)
05-05 08:32:08.227 31602 32198 D WireGuard/GoBackend/RemoteAccesss:
Routine: TUN reader - stopped
05-05 08:32:08.228 31602 32198 D WireGuard/GoBackend/RemoteAccesss:
Routine: receive incoming IPv4 - stopped
05-05 08:32:08.228 31602 32199 D WireGuard/GoBackend/RemoteAccesss:
Routine: receive incoming IPv6 - stopped
05-05 08:32:08.228 31602 31629 D WireGuard/GoBackend/RemoteAccesss:
peer(MqVe…+q28) - Stopping...
05-05 08:32:08.228 31602 32198 D WireGuard/GoBackend/RemoteAccesss:
peer(MqVe…+q28) - Routine: sequential receiver - stopped
05-05 08:32:08.229 31602 32198 D WireGuard/GoBackend/RemoteAccesss:
peer(MqVe…+q28) - Routine: sequential sender - stopped
05-05 08:32:08.229 31602 31629 D WireGuard/GoBackend/RemoteAccesss:
Device closed
05-05 08:32:08.229 31602 32422 D WireGuard/GoBackend/RemoteAccesss:
Routine: decryption worker - stopped
Would that affect the disconnecting of the tunnel ?
Has anyone had this issue with the client not actually disconnecting ?
Any way to get this resolved ?
Thanks
next reply other threads:[~2021-05-05 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 7:47 tomt [this message]
2021-05-06 8:55 ` Jason A. Donenfeld
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=f4166ec7d77fa22bdd727edafe9c58ad@adslweb.co.uk \
--to=tomt@adslweb.co.uk \
--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).