Problem with iwi (ipw2200) + wpa (psk) on snv_78
DESCRIPTION:
Upgraded my wireless network from no security to wpa-psk over the holidays. I
have
a HP dv1000 (model dv1315cl) triple booting Vista/Fedora 8/Solaris SXDE
(snv_70b). The
upgrade worked fine for windows and linux, but snv_70b would not connect via
wpa-psk
(it was working without wpa). The opensolaris forums suggested that snv_78
would solve
the wpa-psk issue I was having with ipw2200/iwi/wpa (message id 189808/quaker).
I
reinstalled Solaris SXDE build snv_78, but seem to have the same iwi+wpa
(non)connection
problems. nwam service is running at boot and displays available wireless AP's,
so it
would appear the iwi driver is working properly. Trying to set the wpa key via
the
nwam "pop-up" or through dladm and starting manually provide the same type of
"not
supported" error message.
ACTIONS:
After logging in, nwam "pop-up" displays available networks. I try to connect
to my
wireless AP and a new "key pop-up" appears. I enter wpa-psk key. No connection
occurs and a new nwam "pop-up" appears. Repeat. New nwam "pop-up" appears,
tried the
"Other" option from the nwam reoccuring "pop-up" and it created a new "secobj"
but did not connect. I rolled up my sleeves and proceeded to the command
terminal.
Disabled nwam (svcadm disable nwam). No more "pop-ups" :)
Check output from /var/adm/messages:
bash-3.2# cat /var/adm/messages | grep iwi
--->snip data prior to last boot--->
Jan 5 19:15:41 dv1315-sol mac: [ID 469746 kern.info] NOTICE: iwi0 registered
Jan 5 19:15:43 dv1315-sol iwi: [ID 451854 kern.warning] WARNING: iwi0:
ipw2200_master_stop(): timeout
Jan 5 19:17:59 dv1315-sol nwamd[28]: [ID 459249 daemon.error]
connect_chosen_lan: connect to 'ap4me' failed on 'iwi0': operation not supported
<---
Check ifconfig info:
bash-3.2# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232
index 1
inet 127.0.0.1 netmask ff000000
rtls0: flags=201000842<BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 18
inet 0.0.0.0 netmask 0
ether 0:c0:9f:a9:45:e8
iwi0: flags=201000802<BROADCAST,MULTICAST,IPv4,CoS> mtu 1500 index 19
inet 0.0.0.0 netmask 0
ether 0:12:f0:83:f7:1a
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252
index 1
inet6 ::1/128
Use dladm to check status of iwi0:
bash-3.2# dladm show-wifi
LINK STATUS ESSID SEC STRENGTH MODE SPEED
iwi0 disconnected -- -- -- -- --
bash-3.2# dladm scan-wifi
LINK ESSID BSSID/IBSSID SEC STRENGTH MODE SPEED
iwi0 2WIRE086 0:1b:5b:21:af:f9 wpa good g 54Mb
iwi0 ap4me 0:14:6c:9b:94:26 wpa very good g 54Mb
iwi0 -- 0:9:5b:9a:a8:98 none very good b 11Mb
bash-3.2# dladm show-linkprop iwi0
LINK PROPERTY VALUE DEFAULT POSSIBLE
iwi0 channel 11 -- --
iwi0 powermode ? off off,fast,max
iwi0 radio on on on,off
iwi0 speed -- --
1,2,5.5,6,9,11,12,18,24,36,48,54
iwi0 zone -- -- --
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:
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
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
_______________________________________________
networking-discuss mailing list
[email protected]
