wpa_cli event handling

Paul Fox pgf at brightstareng.com
Fri Jan 6 10:49:48 EST 2006

 > On Thursday 05 January 2006 04:55, Jouni Malinen wrote:
 > > On Mon, Jan 02, 2006 at 09:50:41AM -0500, Paul Fox wrote:
 > > > i would think that passing an (optional) identifier of some sort
 > > > from wpa_supplicant (via wpa_cli) to the event handler would make
 > > > this cleaner.  i'm picturing something similar to the pcmcia
 > > > "scheme" ID:  a stanza in the wpa_supplicant config file would
 > > > include a "scheme=xxx" line (e.g. "scheme = home", "scheme =
 > > > work", "scheme = use_ZCIP").  (and of course many network stanzas
 > > > might reference the same scheme ID.)  if the scheme (or whatever
 > > > it's called) parameter were present in the config, it would be
 > > > passed as a new third argument to the action script
 > >
 > > I don't have anything against adding something like this if there is
 > > enough interest on it and someone would really use it. This means
 > > changing an event message from wpa_supplicant, so the accepted strings
 > > would likely be quite limited in what is allowed (e.g., just
 > > alpha-numeric characters and underscore; no spaces etc.).
 > If you do this, please just export variables to the shell instead of appending 
 > them as arguments.
 > This allows us to remove/add variables at will instead of fixing them to arg1 
 > ACTION, arg2 SSID, arg3 ENCTYPE, etc etc

good point.

jouni -- i would definitely use this feature.  i took a look at adding
it myself the other day, so i could send you a patch, but quickly realized
that i'd almost certainly get it wrong, which would probably worse
for you than not helping at all.  :-)

(and limiting the acceptable strings for the scheme id is fine, of course.
alphanumeric and even length-limited would be fine.)

 paul fox, pgf at brightstareng.com

More information about the HostAP mailing list