Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Ticket #322 (new defect)

Opened 16 years ago

Last modified 15 years ago

Promiscuous broken

Reported by: anonymous Assigned to:
Priority: minor Milestone: version 1.0.0 - first stable release
Component: madwifi: other Version: trunk
Keywords: Cc:
Patch is attached: 0 Pending:

Description

When I enable promiscuous when using, say, Ethereal, the card only seams to capture packets comming from the AP, but not from the peers in the same network.

Change History

01/22/06 10:39:08 changed by mrenzmann

  • priority changed from major to minor.
  • milestone changed from version 0.9.0 - move to new codebase to version 1.0.0 - first stable release.

Which revision does that refer to?

As a work-around you might want to make use of a VAP in monitor mode.

02/15/06 20:36:01 changed by anonymous

  • patch_attached changed.

madwifi-ng-r1401-20060117

monitor mode however doesn't seam to play nice with WEP.

02/16/06 08:57:13 changed by mrenzmann

Please try a more recent version and see if the problem still exists there. In addition, could you please be a bit more specific about "doesn't seem to play nice with WEP"?

02/16/06 23:21:11 changed by anonymous

sure, I'll update my version I do that every month :)

I mean by "doesn't seem to play nice with WEP" that, after creating a monitor interface (regarless wether I delete all the current interfaces or not), and I open ethereal and dump the output, I get garbage (since the WEP key isn't set at that point).

When I do setup the key by iwconfig ath0 key insert-key-here, my computer crashes at the moment I execute the command.

I must be doing something wrong...

I could always just dump the unencrypted packets, and then unencrypt them using some tool available, but it's a lot less practical.

thanks for your support :)

02/17/06 06:12:34 changed by mrenzmann

Can you please provide a full, decoded dump of the oops message you get when you try to set the WEP keys? That would probably help to locate the problem. See DevDocs/KernelOops for more information.

04/27/06 19:10:36 changed by dyqith

Any updates ?

thanks.

03/03/07 18:40:49 changed by anonymous

I have excactly the same issue when capture packets using tcpdump or ethereal. I use the lastest version of madwifi-ng. This means the current version from today. The only packets I am able to capture are the ones send from the AP to the client system. So as an example starting tcpdump -i ath0 -n icmp I only the the ICMP Reply and never the ICMP Request. Any help would be fine....