wpa_cli event handling

[Paul Fox]

in another thread, i asked:
 > > can i ask a semi-related question?  i didn't see it in the docs
 > > or the example config, but i'm a few revs out of date -- does
 > > wpa_supplicant have any hooks for running scripts after
 > > association, which could be used for interface configuration?
 > 
 > To answer that specific question, wpa_cli can be launched as a daemon that 
 > runs monitors wpa_supplicant and runs a script based on wpa_supplicant 
 > actions.

i haven't tried this feature yet, but i've read the docs

but i have a simple question:  why isn't the action script that's 
invoked passed the ssid of the network that's been joined?  right
now the script gets the interface name, and dis/connected status. 
the very first thing the action script will probably have to do
is ask the interface what network it's on.  i'm sure there was a
reason for leaving this information out of the the script
transaction, but i'm curious what it was.  was it just to keep
the script interface to the absolute minimum?

(in case i'm not clear, the problem i want to solve is the simple
"roaming between known networks" problem, where some require
configuration with dhcp, some with static, etc.)

paul
=---------------------
 paul fox, pgf at brightstareng.com