On Wed, May 30, 2007 at 12:30:47AM +0200, Casper.Dik at Sun.COM wrote: > > >For 802.11 (mac_wifi type devices), its not entirely clear what is most > >desirable. We have SSID, security information (WEP/WPA, open/shared-key > >auth -- though nobody should ever use shared-key), 802.11 "mode" > >(802.11b/802.11g, 802.11a), Infrastructure vs. Adhoc, frequency/channel, > >current rate (though that can change at any time). Additionally, even > >the notion of associated/authenticated is a bit muddied by 802.11. > > > >What I'd like to do is leave the other non-802.3 messages as just "link > >up", with no further details. > > What I found usable when working on wifi drivers were message of > the form: > > linkup, X% signal strange, ESSID="XXXX" > > each type of link has its own significant information.
Agreed. But presumably the log message for wireless NIC state change shouldn't be issued for every signal strength change! Just when signal strength goes aboe zero (link up) or down to zero (link down). And NWAM might not want to try to do things just because the link on a wireless interface went down -- I may be walking somewhere and be back within range of a base station soon. I agree that the base station ID is useful to have in these messages. OT: What about the little button that some systems (laptops, mostly?) have to enable/disable wireless? How should Solaris deal with that? Because if I turn off wireless then I definitely want NWAM to do something about that, but if signal strength temporarily falls to zero then I probably don't want NWAM to do anything about that. So mapping both, that button and signal strength to link up/down status is probably a bad idea. Nico --
