Hi Steve,

Steve Forster wrote:
> Problem with iwi (ipw2200) + wpa (psk) on snv_78
>
> ...  
>
> Manually add a new "secobj":
> bash-3.2# dladm create-secobj -c wpa ap4mepsk
> (enter psk password/confirm) 
>
> bash-3.2# dladm show-secobj
> OBJECT               CLASS                
> nwam-ap4me-0.14.6c.9b.94.26 wpa                  
> nwam-ap4me           wpa                  
> ap4mepsk             wpa       
> (First two show objects created with nwam, third manually created)
>
> Manually try to connect to wireless AP with dladm:
>   
Did your AP configured as WPA/TKIP or WPA/CCMP?
> First, make sure it's not connected to anything -
> bash-3.2# dladm disconnect-wifi iwi0
> dladm: cannot disconnect link 'iwi0': not connected
>
> Second, try to connect with manually created secobj -
> bash-3.2# dladm connect-wifi -e ap4me -s wpa -k ap4mepsk iwi0
> dladm: cannot connect link 'iwi0': operation not supported
>   
Try # dladm connect-wifi -e ap4me -k ap4mepsk iwi0
Please make sure the nwam service is disabled.

--
Quaker
> Next, I tried changing the "/etc/nwam/llp" from default:
> rtls0 dhcp
> iwi0  dhcp
>
> To static IP addresses:
> iwi0    static  192.168.0.123/24
> rtls0   static  192.168.0.234/24
>
> Reran the "dladm connect-wifi" command (above) with no change in outcome.
>
> I've run out of things to try?!? Here's my "uname" output to confirm the SXDE 
> running -
> bash-3.2# uname -X
> System = SunOS
> Node = dv1315-sol
> Release = 5.11
> KernelID = snv_78
> Machine = i86pc
> BusType = <unknown>
> Serial = <unknown>
> Users = <unknown>
> OEM# = 0
> Origin# = 1
> NumCPU = 1
>
>
> RESOLUTION: ???
>
> Have I missed something here? Is there a patch required, does snv_78 not 
> provide
> wpa with iwi (ipw2200)?
>
> Any suggestions would be greatly appreciated in resolving this matter. Thanks 
> in
> advance for your comments/suggestions!
>
> Steve
>  
>  
> This message posted from opensolaris.org
> _______________________________________________
> laptop-discuss mailing list
> laptop-discuss at opensolaris.org
>   


Reply via email to