I'm trying to get the iwi driver working on my Thinkpad T43 with WPA2.
This is with Solaris Express Community edition snv_81


When I run  
dladm connect-wifi -e myessid  -k home_wifi -s wpa

I establish a connection with the AP. 
#dladm show-secobj
OBJECT               CLASS                
test                 wpa                  
home_wifi            wpa                  
nwam--0.1a.70.d6.eb.c4 wpa  


If I use the wrong key it doesn't work.
I also see EAPOL Key messages going back and forth between the laptop
and the AP if I ran tshark on another machine.

# dladm show-wifi
LINK       STATUS            ESSID               SEC    STRENGTH   MODE   SPEED
iwi0       connected         myessid            wpa    excellent  g      --
# 
I then configure the interface with
ifconfig iwi0 192.168.1.4 netmask 255.255.255.0 
# ifconfig iwi0
iwi0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
        inet 192.168.1.4 netmask ffffff00 broadcast 192.168.1.255
        ether 0:13:ce:80:e2:35 
however I can't ping the ap

When I try I see the packet count increasing on the route with a netstat -r
netstat -r -n

Routing Table: IPv4
  Destination           Gateway           Flags  Ref     Use     Interface 
-------------------- -------------------- ----- ----- ---------- --------- 
default              192.168.1.1          UG        1          8           
192.168.1.0          192.168.1.4          U         1         10 iwi0      
127.0.0.1            127.0.0.1            UH        1       8210 lo0       

but the outgoing packet count on the interface doesn't change and I don't
see any traffic from the laptop with the sniffer on the wifi link.
^C# netstat -i -n
Name  Mtu  Net/Dest      Address        Ipkts  Ierrs Opkts  Oerrs Collis Queue 
lo0   8232 127.0.0.0     127.0.0.1      12672  0     12672  0     0      0     
iwi0  1500 192.168.1.0   192.168.1.4    484    0     2      0     0      0     


Any ideas?

The AP is configured to use aes+tkip.
 
 
This message posted from opensolaris.org

Reply via email to