Ehud, I was just reviewing the complete dmesg output that you sent earlier, which I think was for a "bad" case. I use WPA encryption, which cannot be done in hardware, and I have not seen messages that look like this:
bcm43xx-phy0 debug: Using hardware based encryption for keyidx: 0, mac: ff:ff:ff:ff:ff:ff eth1: Initial auth_alg=0 eth1: authenticate with AP 00:0d:88:ac:b2:2a eth1: RX authentication from 00:0d:88:ac:b2:2a (alg=0 transaction=2 status=0) eth1: authenticated eth1: associate with AP 00:0d:88:ac:b2:2a eth1: RX AssocResp from 00:0d:88:ac:b2:2a (capab=0x431 status=0 aid=1) eth1: associated eth1: switched to short barker preamble (BSSID=00:0d:88:ac:b2:2a) ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready In particular, I mean the "hardware based encryption", and the "short barker preamble" messages. Please boot a "good" kernel and save the dmesg output. Do the same for a "bad" kernel. Send the two sets of dmesg output, and iwconfig and ifconfig output for the bad one. In the meantime, I'll configure my spare AP for WEP encryption and see what I get in my logs. Thanks, Larry _______________________________________________ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
