wpa_cli event handling (revisited)

Roy Marples uberlord at gentoo.org
Tue May 30 06:16:12 EDT 2006


On Tuesday 30 May 2006 10:18, Reinhard Tartler wrote:
> > Just out of curiosity, can ifupdown handle this?
>
> The problem is that ifupdown records the 'state' of an interface:
> > ifup eth0 (or some other trigger)
>
> You mean e.g. a cardbus card has been inserted and udev triggers a ifup
> eth0.
>
> > netplugd is launched
> > netplugd triggers ifup eth0 as cable is in
>
> ifup will fail with 'interface already configured'
>
> > wpa_supplicant is launched with -Dwired on eth0
> > wpa_cli triggers final ifup eth0
>
> and here again.
>
> > Just curios as I had a forum request for Gentoo to handle that and it
> > took some time to get it working as all enterance points from daemons are
> > net.eth0 start.
>
> The problem here is to define what 'configuring an interface' actually
> means, because ifupdown has its own POV about this.

I would like to know how is problem - if it is indeed perceived to be a 
problem is solved then :)

-- 
Roy Marples <uberlord at gentoo.org>
Gentoo/Linux Developer (baselayout, networking)



More information about the HostAP mailing list