Kismet Wireless

Kismet Forums

 

Posted by:aclinux
Subject:orinoco-0.13-dragorn-2.6.17 shared key problems
Date:18:42:00 01/09/2006

More info here.

With "in-kernel" drivers:

iwconfig eth2

Warning: Driver for device eth2 has been compiled with version 20
of Wireless Extension, while this program supports up to version 19.
Some things may be broken...

eth2 IEEE 802.11b ESSID:"XXXX" Nickname:"XXXX"
Mode:Managed Frequency:2.457 GHz Access Point: 00:14:BF:04:57:EF
Bit Rate:2 Mb/s Sensitivity:1/3
Retry limit:4 RTS thr:off Fragment thr:off
Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX Security mode:restricted
Power Management:off
Link Quality=36/92 Signal level=-59 dBm Noise level=-95 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

With backported drivers:

iwconfig eth2

Warning: Driver for device eth2 has been compiled with version 20
of Wireless Extension, while this program supports up to version 19.
Some things may be broken...

eth2 IEEE 802.11-DS ESSID:"XXXX" Nickname:"XXXX"
Mode:Managed Frequency:2.442 GHz Access Point: None
Bit Rate:11 Mb/s Tx-Power=15 dBm Sensitivity:1/3
Retry limit:4 RTS thr:off Fragment thr:off
Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX
Power Management:off
Link Quality=0/92 Signal level=134/153 Noise level=134/153
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

The diferences:
a) No association to AP.
b) Nothing about security mode.
c) Link (obviously) quelity=0.

Regards


> The backported drivers works fine with kismet (at least numbers and networks apperars in the screen).
>
> The problem I found is when I use this:
>
> iwconfig eth2 key restricted
>
> I don't see the "encrypted" when I run:
>
> iwconfig eth2
>
> I use WEP-104 + SHARED KEY.
>
> The "in-kernel" driver, works, but the backported driver not.
>
> I tried use it with wpa_supplicant and the problem persist.
>
> The iwconfig commands to config the wep and the network connections works fine with the "in-kernel" driver, but not with the backported one.
>
> Kismet doesn't work with "in-kernel", but it works fine with backported one.
>
> Is this a known issue?
>
> Kernel: 2.6.17.x
>
> Regards


Reply to this message