| 1 |
On 6/5/2008 4:49 PM Eric Martin said the following: |
| 2 |
> Drew Tomlinson wrote: |
| 3 |
>> Ever since I upgraded my gentoo-sources kernel from 2.6.23 to 2.6.25, |
| 4 |
>> I can no longer see packets on my wireless network for any device |
| 5 |
>> other than my own. The tcpdump output looks like this: |
| 6 |
>> |
| 7 |
>> 20:49:32.909144 00:12:bf:2a:2c:76 (oui Unknown) Unknown SSAP 0x10 > |
| 8 |
>> 00:1f:32:5f:fe:06 (oui Unknown) Unknown DSAP 0xc2 Unnumbered, disc, |
| 9 |
>> Flags [Final], length 44 |
| 10 |
>> 20:49:32.912775 00:12:bf:2a:2c:76 (oui Unknown) Unknown SSAP 0x10 > |
| 11 |
>> 00:1f:32:5f:fe:06 (oui Unknown) Unknown DSAP 0xc2 Information, send |
| 12 |
>> seq 42, rcv seq 0, Flags [Response], length 204 |
| 13 |
>> 20:49:32.916874 00:12:bf:2a:2c:76 (oui Unknown) Unknown SSAP 0x10 > |
| 14 |
>> 00:1f:32:5f:fe:06 (oui Unknown) Unknown DSAP 0xc2 Supervisory, |
| 15 |
>> Receiver not Ready, rcv seq 0, Flags [Response], length 169 |
| 16 |
>> 20:49:32.976738 00:12:bf:2a:2c:76 (oui Unknown) Unknown SSAP 0x10 > |
| 17 |
>> 00:1f:32:5f:fe:06 (oui Unknown) Unknown DSAP 0xc2 Information, send |
| 18 |
>> seq 43, rcv seq 0, Flags [Response], length 64 |
| 19 |
>> 20:49:33.047570 00:12:bf:2a:2c:76 (oui Unknown) > 00:1f:32:5f:fe:06 |
| 20 |
>> (oui Unknown), ethertype Unknown (0x05ec), length 1530: |
| 21 |
>> 0x0000: c211 5700 c393 1b7b 838f 366c 27c5 f97a ..W....{..6l'..z |
| 22 |
>> 0x0010: 5111 7d1a 1e33 bebd a432 ff30 5a35 e0ad Q.}..3...2.0Z5.. |
| 23 |
>> 0x0020: ba16 2b31 f1e9 d905 5967 f333 d3a1 4ba3 ..+1....Yg.3..K. |
| 24 |
>> 0x0030: 1e32 0f18 fcc2 |
| 25 |
>> |
| 26 |
>> I've Googled for an answer and think that my problem is that I am |
| 27 |
>> unable to decrypt WEP packets for any device other than my own. This |
| 28 |
>> is a simple 64 bit WEP network in my home. Unfortunately I did not |
| 29 |
>> find anything that applied to my situation. |
| 30 |
>> |
| 31 |
>> One thing different about my new kernel config is that because I have |
| 32 |
>> a Broadcom card, I moved to the new b43 driver instead of the old |
| 33 |
>> b43_legacy driver. I am using version 4 firmware however I had the |
| 34 |
>> same problem with version 3 firmware. I was hoping that would fix it |
| 35 |
>> but no luck. |
| 36 |
>> |
| 37 |
>> I am also using the new MAC80211 stack instead of the older IEEE80211 |
| 38 |
>> stack. |
| 39 |
>> |
| 40 |
> I don't have much help to offer than go with WPA over WEP (especially |
| 41 |
> WEP64). A guy at my LUG gave a presentation on hacking WEP and did it |
| 42 |
> in under 1 minute. I went home that night and got WPA to work. |
| 43 |
|
| 44 |
Agreed that WEP is only marginally better than wide open. However I am |
| 45 |
using an old Linksys ethernet/wireless bridge that does not support |
| 46 |
WPA. Plus this is my small home network on property that is not that |
| 47 |
close to others. Add to that MAC filtering (again, not hard to crack) |
| 48 |
and I feel that the likelihood of someone seeking me out and cracking my |
| 49 |
network is unlikely. And even if someone did, what are they going to |
| 50 |
get? They'd still have to crack each system on my net before finding my |
| 51 |
MP3s and family photos. |
| 52 |
|
| 53 |
>> Any ideas on what I have done wrong? |
| 54 |
> Yes, turning on wep vs WPA ;) |
| 55 |
|
| 56 |
For me, WEP isn't wrong. Just an educated choice based upon my hardware |
| 57 |
capability and security needs. Yours may be different. |
| 58 |
|
| 59 |
> |
| 60 |
>> |
| 61 |
>> Thanks, |
| 62 |
>> |
| 63 |
>> Drew |
| 64 |
>> |
| 65 |
> Sorry the only answer is do it totally differently but nobody else |
| 66 |
> replied so I figured I'd chime in. |
| 67 |
Thanks for the suggestion, |
| 68 |
|
| 69 |
Drew |
| 70 |
|
| 71 |
|
| 72 |
-- |
| 73 |
Be a Great Magician! |
| 74 |
Visit The Alchemist's Warehouse |
| 75 |
|
| 76 |
http://www.alchemistswarehouse.com |
| 77 |
|
| 78 |
-- |
| 79 |
gentoo-user@l.g.o mailing list |
Archives