From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: jedi_papi@yahoo.com Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id fc600b81 for ; Sat, 2 Jun 2018 21:27:14 +0000 (UTC) Received: from sonic302-49.consmr.mail.gq1.yahoo.com (sonic302-49.consmr.mail.gq1.yahoo.com [98.137.68.175]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 41992296 for ; Sat, 2 Jun 2018 21:27:14 +0000 (UTC) Date: Sat, 2 Jun 2018 21:25:09 +0000 (UTC) From: Jose Marinez To: WireGuard Mailing List Message-ID: <1075455406.8212220.1527974709121@mail.yahoo.com> Subject: Android error, fix and next steps MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_8212219_1144090130.1527974709119" References: <1075455406.8212220.1527974709121.ref@mail.yahoo.com> List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , ------=_Part_8212219_1144090130.1527974709119 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hello guys, I encountered this error while testing on a LG V30 running Oreo. "Error binging up tunnel: VPN service not authorized by user" It turned out that due to an existing StrongSwan installation, the Wireguard client could not work. The fix involved deleting the StrongSwan client from the phone. Next steps: I can't imagine the Wireguard client to expect exclusivity as the sole VPN client to run on any device. In the case of StrongSwan, it had an "Always On" setting which I believe prevented Wireguard from making network changes. What's the best way to approach this? I don't want to assume this is a Wireguard Android client bug. Perhaps on Android only one client can have the "always on" setting at once. Any clarity on this would help, to at a minimum figure out which party to approach: Google vs. StrongSwan vs. Wireguard Thanks,Jose ------=_Part_8212219_1144090130.1527974709119 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello guys,

I encountered this error while te= sting on a LG V30 running Oreo.

"Error binging up tunne= l: VPN service not authorized by user"

It turned out tha= t due to an existing StrongSwan installation, the Wireguard client could no= t work. The fix involved deleting the StrongSwan client from the phone.

Next steps:

I can't imagine the Wireguard client to exp= ect exclusivity as the sole VPN client to run on any device. In the case of= StrongSwan, it had an "Always On" setting which I believe prevented Wiregu= ard from making network changes.

What's the best way to approach this? I don't want to ass= ume this is a Wireguard Android client bug. Perhaps on Android only one cli= ent can have the "always on" setting at once.

Any clarity on this would help, to at a min= imum figure out which party to approach: Google vs. StrongSwan vs. Wireguar= d


Thanks,
Jose
------=_Part_8212219_1144090130.1527974709119--