Thanks for all the info Mike -- I'll let the NWAM guys answer your considerable input on the phase-0 feature set :-)
> > How much work do you think the transition from wificonfig to dladm would > > be? Is there some way we can assist? > > The wireless code in inetmenu is pretty modular (and simple), so it > would be trivial to implement. (Once I figure out how to use dladm.) If > someone points me to a cheatsheet of how to use dladm on the command > line to scan, and connect, I'd be set. It'll be ready by Monday. :-) Wow, great! The manpage is probably the closest thing to a cheatsheat, but to briefly summarize, you just use the scan-wifi and connect-wifi subcommands. You'll probably also need to check out create-secobj, which allows you to create persistent WEP and WPA keys that you can then pass to connect-wifi. (Keep in mind that unlike wificonfig, dladm does not have any notion of profiles, and none of the WiFi-specific subcommands are persistent or track history.) Since you're probably parsing the output for scan-wifi, you'll want to use the -p (parseable output) mode along with the -o option to specify the fields you want to output. The parseable format isn't ideal for ksh scripts, but it shouldn't be too hard to get the information you need. -- meem
