iwlist scan output incorrect?

[scott]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Vitorio Okio wrote:
> On Mon, 17 Mar 2008 17:51:44 -0600, jim barnes wrote:
> 
>> On Monday 17 March 2008 15:10:40 Vitorio Okio wrote:
>>> Yes the settings are in nvram.  Here is the output:
>>>
>>> ~#nvram show | grep aes
>>> wl_crypto=aes
>>> wl0_wds0=*,auto,aes,psk2,MyESSID,This_Is_My_Passphrase wl0_crypto=aes
>> Gosh, at this point I think a second opinion from a third party is in
>> order... Preferably one with a different wireless card, who can verify
>> the output of iwlist ethx scanning (or equivalent?).
>>
>> I'm siding with the router config!
> 
> Well, considering the following I think the problem is either in 'iwlist' 
> or in my card reporting to 'iwlist' incorrectly.
> 
> Again, here is my DD-WRT router nvram:
> 
> ~ # nvram show | grep aes
> wl_crypto=aes
> wl0_wds0=*,auto,aes,psk2,MySSID,xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx
> wl0_crypto=ae
> 
> Here is output of 'sudo iwlist eth1 wpakeys':
> 
> user at hostname:~$ sudo iwlist eth1 wpakeys
> eth1      2 key sizes : 40, 104bits
>           4 keys available :
>                 [1]: xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx (128 bits)
>                      Address: 00:00:00:00:00:00
>                      Algorithm: CCMP                 Flags: 0x00000001
>                         tx-seq-valid
>                 [2]: xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx (128 bits)
>                      Address: 00:00:00:00:00:00
>                      Algorithm: CCMP                 Flags: 0x00000001
>                         tx-seq-valid
>                 [3]: xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx (128 bits)
>                      Address: 00:00:00:00:00:00
>                      Algorithm: CCMP                 Flags: 0x00000001
>                         tx-seq-valid
> Error reading wpa keys (SIOCGIWENCODEEXT): Invalid argument
>           Current Transmit Key: [1]
> 
> And here is output of 'sudo iwlist eth1 genie':
> 
> user at hostname:~$ sudo iwlist eth1 genie
> eth1    
>                     IE: IEEE 802.11i/WPA2 Version 1
>                         Group Cipher : TKIP
>                         Pairwise Ciphers (1) : TKIP
>                         Authentication Suites (1) : PSK
> 
> You can clearly see that the last 2 iwlist outputs are in complete 
> contradiction each with other (note CCMP vs TKIP reported).
> 
> In addition I had this rendig:
> 
> user at hostname:~$ sudo lsmod | grep aes
> aes                    28608  3
> 
> While both these rending nothing:
> 
> user at hostname:~$ sudo lsmod | grep ieee80211_crypt_tkip.ko
> user at hostname:~$ sudo lsmod | grep ieee80211_crypt_tkip
> 
> That is, the only encryption related module loaded while I'm connected is 
> 'aes' module.
> 
> Thus I'm quite positive now that I'm connecting using WPA2-PSK/AES. And 
> the problem is as stated above: either in iwlist or in bcm43xx reporting 
> incorrectly. Actually this line in the iwlist output above probably 
> supports the last suggested:
> 
> "Error reading wpa keys (SIOCGIWENCODEEXT): Invalid argument"
> 
> 
> 
Sounds like a compatibility issue between the card's chipset in your box
and the chipset in the router.

Handshakes through the registers may be at different offsets.

B**ch, isn't it?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH31F9s+9h2X0fCGcRAlkHAKCUNMD1+3hPDx26n3bYO6s41n2oHwCfZhH6
eVst3FfyW2aFc8TbvIJ+t6s=
=WVhv
-----END PGP SIGNATURE-----