Hi, I have tried to reproduce the problem (WPA2 4-way handshake) but I can't reproduce it here. I have tried to 
associate to an access point with the short preamble ability (as the one you are using has this ability) and also 
another access point without the short preamble ability. Also besides the io-pkt-v4-hc (that is what you are running), I
 have also tried another flavor like io-pkt-v6. They all work fine. 

So I think it would be better to solve/understand the following two suspectable points. I also listed my wpa conf file 
at the end and attached my log of accessing an WPA2+psk access point. Hope it be helpful.

1) the ifconfig got blocked (although ^C can make it free). I can't see it on my side either. Can you check the pidin to
 see what is the status of the io-pkt? I noticed in you very first email, there is a script, (?) bt_detect? where you 
have one io-net and two io-pkt instance running? If you intended to run more than one instances of io-net and/or io-pkt,
 you have to use the prefix option, otherwise, neither of them work as expected. Anyway, please use pidin to see if any 
suspectable point. I think we'd better to solve it first (ifconfig blocks) and go further onto such as wpa2.

==== the section in your script ?? ===============
/usr/sbin/random

#/proc/boot/io-net -ptcpip -ppppmgr &

/proc/boot/waitfor /dev/random 4

#/sbin/io-pkt-v4-hc random -ptcpip -pppmgr &

/platform/bin/wd &

/platform/bin/pm &

/platform/bin/doc &

/platform/bin/adi &

/proc/boot/waitfor /dev/pm/wifi/controls/enable 4

/sbin/pci-lge5200b

/proc/boot/waitfor /dev/pci 4

/sbin/io-pkt-v4-hc random -dath -ptcpip -pppmgr &

====================


2) I noticed there is more than 1 second between the broadcast and the first message sending to your access point. It 
might indicate a problem of difficulty of accessing your access point. You may run "ifconfig ath0 scan" to see if you 
can get the list of wireless devices around you and please check if the signal of your access point is too weak. Also 
please check your access configuration settings and make sure it is correct. (I blindly suspect the signal is too weak 
on your side and if it is the case, move closer to your access point and try again ...)

I list below the wpa.conf that I am using and the attached is the log file that the io-pkt+ath successfully associated 
to my access point (Linksys Wireless-G WRT54GS).

=== my wpa2.conf ===
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1
ap_scan=1

network={
       ssid="linksys"
#	proto=RSN 
	proto=WPA2
       key_mgmt=WPA-PSK
#       pairwise=CCMP TKIP
#       group=CCMP TKIP
       psk="LINKSYSWPAKEY"
}
===================

Hi Robert,

I think I need to give more background of this project. The nature of it is to port our wpa_supplicant to QNX platform 
on top of io-pkt stack.
 
The hardware and the kernel come with it are from our customer;  these network issues has been found on this particular 
target, therefore I dont think they can be reproduced on a different type of target.

The network subnet envrionment is pretty standard, and works fine with all other devices that has been connected with --
 including different type board/cpu/wireless driver, for example, we have put a PPC board running QNX 6 with io-net 
network stack and a Broadcom chip on the same subnet, it can shoot big buffer packets no problem at all (up to the limit
 65K); so I wouldn't suspect the subnet too much, (let me know if this makes sense). 

I have requested our customer to reproduce the problem on same configuration target, but I have not gotten results back;
 

I suspect the problem is related to network configuration while building the kernel or some memory issues specific to 
this board -- any advice regarding this perspective? Or have you encountered similar problems before?


Thanks a lot, 
Regards,
Shannon