jiri sasek - Sun Microsystems - Prague Czech Republic wrote: > ... > > For further reference I am running the Nevada build 86 on sony - vaio > (interface: wpi0). > >> Actually, there is a wpa supplicant in Nevada, act as an SMF service. >> Solaris WiFi driver already supported WPA-PSK since build 64. >> > > I did not know about but currently I have foud the following: > > - here is the /var/svc/manifest/network/wpa.xml manifest > - "svcs wpa" returns nothing > - "svcadm enable wpa" does not change anything > > ...how the supplicant can be setup? "dladm connect-wifi" command will create the WPA service instance dynamically. When you setup a WPA connection, "svcs wpa" will show you the instance. > > I have tested similar procedure with the following modifications > >> # dladm create-secobj -c wpa psk >> --- input your psk --- > > dladm create-secobj -f open_text_file -c wpa psk > > ...because the key here contains the "\'", "\:", "\!"...and similar > symbols and is too complicated to be written "from the hand" without > the typo by me :-) Note that only ascii characters key is supported. > >> >> # dladm connect-wifi -e essid -k psk >> > > dladm connect-wifi -e essid -k psk wpi0 > > output is: > > dladm: no wifi networks with the specified criteria are available > > ...where ESSID is also very complicated and it is also not broadcasted > here on my site but id fortunately does not consist of "strange" > characters. There were previously problem with hidden SSIDs in dladm > AFAIK where the "-e" optval was directly compared (strcmp()) with the > scanned ESSIDs (void in the case of hidden SSID on AP) returning the > same kind of the error message. > > Currently I was checking the dladm code and it looks to be OK. > > Can anybody help with this problem? Ah, maybe you can try nwam.
-- Quaker
