[This is mostly to keep the Debian Bug Tracking system updated, but list
is Cc:ed too] [resent, b/c i messed up]

The below quoted is related to this bug if I don't totally miss
understood it.

I still think it should be a part of the wpa_supplicant executable for
two reasons:

1. Having one additional process just for starting scripts seems like
   resource waste.
2. Having one configuration file for configuring all wireless stuff
   would be better for the user than a bunch of places that have to be
   edited.

For the practical part with this existing code though wpa_cli could be
started with a script that parses a configuration file and chooses what
argument to give to ifup. E.g. "ifup eth0=wifihome"
--
/Martin

On Sat, Apr 23, 2005 at 08:53:01PM -0700, Jouni Malinen wrote:
> On Wed, Apr 20, 2005 at 10:36:52AM +0100, Roy Marples wrote:
> 
> > Attached to this email is a patch to wpa_supplicant CVS which replaces
> > existing Connected, Disconnected and Terminating messages with ones like
> > the above. It also includes a new file, events.h, which defines the text
> > of the messages so that other programs can include it and ensure that
> > the text is an exact match.
> 
> Thanks! I made similar changes to the development version of
> wpa_supplicant. The fixed prefixes are now defined in wpa_ctrl.h.
> 
> > wpa_monitor.c (based loosely off wpa_cli.c) is a new program whose sole
> > purpose is to listen to those three wpa_supplicant events and take
> > appropriate action via a shell script (wpa_monitor.action) which can be
> > customised per OS.
> 
> In order to avoid having similar code in multiple programs, I ended up
> including this kind of functionality in wpa_cli. This is enabled by
> using -a command line argument to select which script to run on the
> connect/disconnect events.
> 
> -- 
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> [EMAIL PROTECTED]
> http://lists.shmoo.com/mailman/listinfo/hostap


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to