Thanks for the ubus pointers, Bastian. That should solve it :)
Johan
On Mon, Nov 17, 2014 at 10:34 AM, Bastian Bittorf bitt...@bluebottle.com
wrote:
* Johan Almbladh j...@anyfi.net [17.11.2014 10:22]:
The hotplug scripts receive events for interface names, but they know
nothing about
* Johan Almbladh j...@anyfi.net [17.11.2014 10:22]:
The hotplug scripts receive events for interface names, but they know
nothing about the underlying configuration. Is there any way to map a WLAN
interface name, e.g. wlan0, to the corresponding UCI config entry in
/etc/config/wireless?
Hi,
I'm trying to start/stop our Wi-Fi sharing daemons [1] in tandem with wifi
up/down. On AA we used to patch /sbin/wifi, but on BB it seems this logic
has moved into netifd and that it may be possible to do it patchless,
perhaps by monitoring ubus for some event?
I tried just doing ubus listen
* Johan Almbladh j...@anyfi.net [12.11.2014 10:45]:
I tried just doing ubus listen in one shell and then running wifi from
another, but that doesn't give much to go on:
which events do you need?
a joining or leaving station?
use 'iw event'
an upcoming (or going down) interface?
use
Thanks, Bastian. If I add a script /etc/hotplug.d/net/ I get up/down events
for WLAN interfaces when /sbin/wifi is run.
The hotplug scripts receive events for interface names, but they know
nothing about the underlying configuration. Is there any way to map a WLAN
interface name, e.g. wlan0, to