If you're running snv_29 then it already has the "machinery". This includes:
1. The wificonfig binary
2. The modification of SMF initialization script so that a WiFi
interface can be configured at startup time.
3. The modification of devfsadm so that a link to the wifi interface is
automatically created under /dev/wifi
4. RBAC for wificonfig.
For example, if there's a /etc/hostname.ath0, then at startup time,
"wificonfig -i ath0 startconf" will be invoked right after the interface
is plumbed by ifconfig. "startconf" is similiar to "autoconf" except
that it doesn't required R/W mount. It selects a pre-configured Profile
according to the Preference List created by the user. Wificonfig
maintains a Preference List (it can be shown by "wificonfig listprefer")
which contains a list of WLANs. So if there are two WLANs in the
Preference List:
office-wifi1
office-wifi2
Then wificonfig tries office-wifi1 first, then office-wifi2. Automatic
configuration can also be done after the system is up and running, by:
$ wificonfig -i <if> autoconf
This tells wificonfig to try the Preference List first, if the
Preference List is empty, it'll use its built-in heuristics to try to
scan and connect to a public (no WEP) WLAN.
Vincent.
Youri Podchosov wrote:
>I have a laptop with a wireless interface being the primary (and the only)
>one. I need it to be brought up at the same time as a wired interface would
>be (i.e. when network/physical service comes up). It doesn't work that way,
>however, as the only way to configure a wireless interface is wificonfig which
>requires R/W mounted /var/run (for device locking). Unfortunately, /var/run
>isn't available until after filesystem/minimal service is done. For now, I
>have wifi initialization running at the end of fs-minimal method, but it's
>certainly just a hack.
>
>So how is all that machinery supposed to work? Will setting of wireless
>connection parameters be added as configuration options for the wifi drivers
>of to ifconfig, so that connection can be established along with plumbing the
>interface (or right after the interface is plumbed)? Or wificonfig will
>eventually be properly integrated into the SMF network initialization sequence?
>
>I know about inetmenu, but it's a different story altogether.
>This message posted from opensolaris.org
>_______________________________________________
>laptop-discuss mailing list
>laptop-discuss at opensolaris.org
>
>
