Date: Wed, 23 Nov 2016 23:30:37 +0800
From: Ivan Tham <pickfire@riseup.net>
To: alpine-user@lists.alpinelinux.org
Subject: Re: [alpine-user] Setting up connman
Message-ID: <20161123153037.42eubsvlnfno5go7@riseup.net>
References: <20161123055156.GB3340@Krypton>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Disposition: inline
In-Reply-To: <20161123055156.GB3340@Krypton>

Hi, I use Arch here. I used Connman but I find it complicated (not sure
if it will autostart). For me, wpa_supplicant works very fine and it is
very fast on boot and easy to setup. I found systemd-resolved eating my
bootup time. (I have to admit systemd's setup are a bit weird)

I would really like to know if Connman uses less power compared to
wpa_supplicant, I really hope to see linux performs better on battery.

On Wed, Nov 23, 2016 at 06:51:58AM +0100, Jens Staal wrote:
>I have been trying to use connman as an alternative to the "networking"
>service. I run Alpine on a laptop, which means that I often have very
>different connections.
>
>I could not get it working by just replacing "networking" with "connman"
>during boot (connmanctl could not activate wifi). Do I need to
>change/remove the wpa_supplicatnt configuration file?
>
>
>There were no good instuctions anywhere (not even the Arch wiki was that
>informative) as far as I could see...
>
>
>As an alternative - is there a way to easily change wifi network using
>wpa_supplicant (the gui did not work for me) and is there a way to make
>the networking startup conditional so that it does not look for eth0 if
>wifi is already established and that it does not look for wifi if there
>is a cable attached to eth0?
>
>Right now about 50% of the boot time is due to network lookup.

-- 
Do what you like, like what you do.  -- Pickfire


---
Unsubscribe:  alpine-user+unsubscribe@lists.alpinelinux.org
Help:         alpine-user+help@lists.alpinelinux.org
---