DomainKey-Signature: a=rsa-sha1; c=nofws; d=toastin.space; h=subject:to
	:references:from:message-id:date:mime-version:in-reply-to
	:content-type:content-transfer-encoding; q=dns; s=ml; b=N9PHf7LE
	Q2eukCmGC9kJfMwtviUbHhYgtVMoPG7yHcixEwvZEvIBrN2usJUqQQHiceURkFQg
	AvUQdM6fu3V0eVrYt1XxFJ0DLOP2ZXvtghGKO7jbEspFhjHA283zySA9IlWL7Cw3
	llEIZYzrtm7PKmtPcf7YEsXfGpmYzIzpyZWBQCTpbPloADZriFwoDhx6MU3LyuRx
	rCQWQNVudmPbMF9XGk5OIY9WHzKZHwR07WVr2At4JiWrNOzISJO2ZZIndvVT7xQQ
	Fst3r388BIrC6erxffI3HzGGBmM+hcSiBWuMwpKJ74kMB1pQigpH3xNzUpYyX2ag
	MSwiehbhwB+SbQ==
Subject: Re: [alpine-user] Launching udhcpc through wpa_cli actions
To: alpine-user@lists.alpinelinux.org
References: <AM6PR0602MB359263D6EC2A893E121EB1E4B1800@AM6PR0602MB3592.eurprd06.prod.outlook.com>
From: Chloe Kudryavtsev <toast@toastin.space>
Message-ID: <99c1b250-4700-0b25-bde2-2420b2320391@toastin.space>
Date: Mon, 14 Jan 2019 20:16:58 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:65.0) Gecko/20100101
 Thunderbird/65.0
Precedence: list
MIME-Version: 1.0
In-Reply-To: <AM6PR0602MB359263D6EC2A893E121EB1E4B1800@AM6PR0602MB3592.eurprd06.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit

On 1/14/2019 10:38 AM, Gert de Best wrote:
> Hi All,

Heya!

> The wiki says:
> With the above configuration, udhcpc will only run once at boot. If the Wifi isn't available then, or the network changes in between, it needs to be notified. This is done through the wpa_cli action script in /etc/wpa_supplicant/wpa_cli.sh

There are currently many issues with wpa_supplicant-related init scripts.

> Failed to connect to non-global ctrl_ifname: (nill) error: No such file or directory

One of them is what wpa_cli and wpa_supplicant actually do not interact, 
and there's no other init script to run.

> Can anyone point me in the right direction to fix this?

You have a couple of options:
1. You can wait until I (or someone else) get(s) around to fixing this, 
and the fix gets merged (though the situation will likely look different 
at that point).
2. You can write your own init scripts (and/or configure the existing 
ones heavily) to provide the mentioned functionality.
3. Use a smarter network manager (not necessarily NetworkManager in 
particular, but any sort of non-constant wireless connection usually 
benefits from one). In this scenario, I'm told connman is highly 
recommended for CLI usage.

The issue with 1 is that that wait may take a long time (for instance, I 
am currently working on getting Alpine's user (and developer) official 
documentation up from 0 to full, which will take a while).

The issue with 2 is you need to thoroughly understand wireless 
networking (e.g copy pasting something someone on the ML writes may 
work, or it may not, and you'll need the knowledge regardless in the 
latter scenario, to understand what went wrong).

The issue with 3 is that the smarter network manager may give you other 
problems.
For instance, as my understanding goes, connman expects that 
wpa_supplicant will be started by itself, but I don't know whether or 
not it provides a specific configuration file, nor how it handled a 
restart of the daemon.

> or the network changes in between
Based on this statement, and the fact that you *connect* to wifi, I'm 
going to assume that your device is not permanently rooted in one spot.

As such I'm going to recommend option 3.

P.S. Technically, wpa_supplicant is currently being replaced by iwd (an 
intel daemon).
We do not currently have a package for it, but adding one is high on my 
todo list (once I finish up with the documentation, which, again, could 
take a while, still).


---
Unsubscribe:  alpine-user+unsubscribe@lists.alpinelinux.org
Help:         alpine-user+help@lists.alpinelinux.org
---