Gentoo Archives: gentoo-user

From: Drew Tomlinson <drew@××××××××××××××.net>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Can't Decrypt WEP Packets After Upgrade From 2.6.23 to 2.6.25
Date: Sat, 07 Jun 2008 21:38:38
Message-Id: 484AFFD6.2020601@mykitchentable.net
In Reply to: Re: [gentoo-user] Can't Decrypt WEP Packets After Upgrade From 2.6.23 to 2.6.25 by Mick
1 On 6/6/2008 2:40 AM Mick said the following:
2 > On Tuesday 03 June 2008, Drew Tomlinson wrote:
3 >
4 >> Ever since I upgraded my gentoo-sources kernel from 2.6.23 to 2.6.25, I
5 >> can no longer see packets on my wireless network for any device other
6 >> than my own. The tcpdump output looks like this:
7 >>
8 >> 20:49:32.909144 00:12:bf:2a:2c:76 (oui Unknown) Unknown SSAP 0x10 >
9 >> 00:1f:32:5f:fe:06 (oui Unknown) Unknown DSAP 0xc2 Unnumbered, disc,
10 >> Flags [Final], length 44
11 >> 20:49:32.912775 00:12:bf:2a:2c:76 (oui Unknown) Unknown SSAP 0x10 >
12 >> 00:1f:32:5f:fe:06 (oui Unknown) Unknown DSAP 0xc2 Information, send seq
13 >> 42, rcv seq 0, Flags [Response], length 204
14 >> 20:49:32.916874 00:12:bf:2a:2c:76 (oui Unknown) Unknown SSAP 0x10 >
15 >> 00:1f:32:5f:fe:06 (oui Unknown) Unknown DSAP 0xc2 Supervisory, Receiver
16 >> not Ready, rcv seq 0, Flags [Response], length 169
17 >> 20:49:32.976738 00:12:bf:2a:2c:76 (oui Unknown) Unknown SSAP 0x10 >
18 >> 00:1f:32:5f:fe:06 (oui Unknown) Unknown DSAP 0xc2 Information, send seq
19 >> 43, rcv seq 0, Flags [Response], length 64
20 >> 20:49:33.047570 00:12:bf:2a:2c:76 (oui Unknown) > 00:1f:32:5f:fe:06 (oui
21 >> Unknown), ethertype Unknown (0x05ec), length 1530:
22 >> 0x0000: c211 5700 c393 1b7b 838f 366c 27c5 f97a ..W....{..6l'..z
23 >> 0x0010: 5111 7d1a 1e33 bebd a432 ff30 5a35 e0ad Q.}..3...2.0Z5..
24 >> 0x0020: ba16 2b31 f1e9 d905 5967 f333 d3a1 4ba3 ..+1....Yg.3..K.
25 >> 0x0030: 1e32 0f18 fcc2
26 >>
27 >> I've Googled for an answer and think that my problem is that I am unable
28 >> to decrypt WEP packets for any device other than my own. This is a
29 >> simple 64 bit WEP network in my home. Unfortunately I did not find
30 >> anything that applied to my situation.
31 >>
32 >> One thing different about my new kernel config is that because I have a
33 >> Broadcom card, I moved to the new b43 driver instead of the old
34 >> b43_legacy driver. I am using version 4 firmware however I had the same
35 >> problem with version 3 firmware. I was hoping that would fix it but no
36 >> luck.
37 >>
38 >> I am also using the new MAC80211 stack instead of the older IEEE80211
39 >> stack.
40 >>
41 >> Any ideas on what I have done wrong?
42 >>
43 >
44 > How do you invoke tcpdump? Are you placing your interface in promiscuous
45 > mode? If you iface is 00:12:bf:2a:2c:76 which one is 00:1f:32:5f:fe:06 ?
46 > The router? Does setting -s 65535 provide more packet info?
47 >
48 As root:
49
50 tcpdump -i wlan0
51
52 My iface is 00:14:a5:fc:3b:b2 and is not shown in my log snippet. In
53 the log snippet, one MAC is my access point and the other is a Wii
54 gaming console.
55
56 Please note that this same command on this same network was just fine
57 when I was running kernel 2.6.23. Problems began when I upgraded to
58 kernel 2.6.25. Thus I suspect there is either some change with .25 or
59 more likely, I turned something on/off in my kernel config that I should
60 not have. I just don't know what that "something" might be.
61
62 Thanks for your reply.
63
64 Drew
65
66 --
67 Be a Great Magician!
68 Visit The Alchemist's Warehouse
69
70 http://www.alchemistswarehouse.com
71
72 --
73 gentoo-user@l.g.o mailing list