From: Christian Hewitt <christianshewitt@gmail.com>
To: Grant Erickson <gerickson@nuovations.com>
Cc: daniel antoine <univac55@gmail.com>, connman@lists.linux.dev
Subject: Re: connman-vpn does'nt work with wireguard
Date: Wed, 24 Apr 2024 18:50:19 +0400 [thread overview]
Message-ID: <5D35F841-0063-422D-B6E6-F2FFBAFFF332@gmail.com> (raw)
In-Reply-To: <A3823C56-1321-4B82-B839-9D4A288AA87E@nuovations.com>
> On 24 Apr 2024, at 6:06 PM, Grant Erickson <gerickson@nuovations.com> wrote:
>
> On Apr 23, 2024, at 11:05 PM, daniel antoine <univac55@gmail.com> wrote:
>> I have installed wireguards-tools on my system and I am able to
>> connect to a VPN server friend with the command wg-quick up 'name of
>> the interface' . The configuration file in /etc/wiregard has a host
>> with a FQDN as blabla.com . It also works if I replace the host by an
>> IP address (IPv4 or IPv6).
>>
>> I have adapted the configuration file in /var/lib/connman-plugin like vpn.config
>>
>> [provider_wireguard]
>> Type = WireGuard
>> Name = vpn
>> Host = balabla.com
>> WireGuard.Address = 10.0.6.5 /24
>> WireGuard.PrivateKey = xxxx
>> WireGuard.PublicKey = zzzz
>> WireGuard.AllowedIPs = 10.0.6.0/24
>> WireGuard.EndpointPort = 51822
>> WireGuard.PersistentKeepalive = 25
>>
>> My display environment is enlightenment. I see the connection "vpn" in
>> the connection window. When I click on it , wg show vpn displays the
>> connection to the server, a ip a command shows an interface wg0 but
>> it drops after some seconds. I can ping the server 10.0.6.1 until it
>> drops.
>>
>> If I replace the FQDN by an IP address in this file , for an IPv4
>> address it makes the wifi connection shutdown and returns. My laptop
>> is connected by wifi to my livebox. If I put an IPv6 address it does
>> nothing, no interface wg0 is created.
>>
>> connmanctl shows the vpn service with the command services and the vpn
>> connection is present in vpnconnection
>>
>> My first question is why connman does not accept an IP address IPv4 or
>> IPv6 . I have compiled wiregard-tools with WITH_BASHCOMPLETION=yes
>> and WITH_WGQUICK=yes
>>
>> After why the connection drops
>
> Daniel:
>
> I wonder if you are running into the same issue as Christian Hewitt <christianshewitt@gmail.com> in the thread "RFC: There Are No Routes for Non-default Services
> “: https://lore.kernel.org/connman/FAB1AC37-E077-4067-B245-5CE862CB22B7@gmail.com/
The distro I work on (LibreELEC) is bundling this patch to revert the change:
https://github.com/LibreELEC/LibreELEC.tv/commit/998f2bcfd5849e3eecda6f753ff5bab68a847aea
This unfortunately means we’re unable to bump ConnMan until things are resolved/adapted upstream.
Grant, did you ever get access to the WireGuard server that I shared working?
Christian
next prev parent reply other threads:[~2024-04-24 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 6:05 connman-vpn does'nt work with wireguard daniel antoine
2024-04-24 14:06 ` Grant Erickson
2024-04-24 14:50 ` Christian Hewitt [this message]
2024-04-24 15:20 ` Grant Erickson
2024-04-24 16:14 ` Grant Erickson
2024-04-24 18:22 ` daniel antoine
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=5D35F841-0063-422D-B6E6-F2FFBAFFF332@gmail.com \
--to=christianshewitt@gmail.com \
--cc=connman@lists.linux.dev \
--cc=gerickson@nuovations.com \
--cc=univac55@gmail.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).