b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Gábor Stefanik" <netrolller.3d@gmail.com>
To: Henry Ptasinski <henryp@broadcom.com>
Cc: Ariel Pedraza <pedrazaa@yahoo.com>,
	"b43-dev@lists.infradead.org" <b43-dev@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: pci id 14e4:4727 (bcm4313) status?
Date: Thu, 4 Nov 2010 22:42:36 +0100	[thread overview]
Message-ID: <AANLkTi=MjDUWSULLmVtRCdp2Hm6mDGe5Gw3D-XXKoakh@mail.gmail.com> (raw)
In-Reply-To: <4CD31B37.3000504@broadcom.com>

2010/11/4 Henry Ptasinski <henryp@broadcom.com>:
> On 11/04/2010 07:39 AM, G?bor Stefanik wrote:
>>
>> On Thu, Nov 4, 2010 at 1:21 PM, Ariel Pedraza<pedrazaa@yahoo.com> ?wrote:
>>>
>>> I have the 14e4:4727 and using the brcm80211, this is an example of what
>>> I get and the status of each commands:
>>>
>>> airmon-ng #ok
>>> airmon-ng stop wlan0 #ok
>>> ifconfig wlan0 #ok
>>> macchanger --mac yy:yy:yy:yy:yy:yy wlan0 #ok
>>> airmon-ng start wlan0 #ok
>>> airodump-ng mon0 #ok
>>> airodump-ng -c canal -w nomarch --bssid xx:xx:xx:xx:xx:xx mon0 ?#ok, no
>>> datas
>>>
>>> In other terminal:
>>> aireplay-ng -1 0 -a xx:xx:xx:xx:xx:xx -h yy:yy:yy:yy:yy:yy mon0 #ok,
>>> autentication succesful
>>> aireplay-ng -3 -b xx:xx:xx:xx:xx:xx -h yy:yy:yy:yy:yy:yy mon0 #ok, supose
>>> to increment datas but NOP!!!
>>>
>>> In other terminal:
>>> aircrack-ng -b xx:xx:xx:xx:xx:xx nomarch.cap #ok, no datas...
>>>
>>> So... when do you think that the brcm80211 implemetation will be ready to
>>> capture datas?
>>
>> Hmm... filter configuration issue? Apparently the "pass other-BSS
>> data" filter flag is not getting written to the hardware. (Do we even
>> have such a flag in the brcm80211 FW?)
>
>>
>> Can you see any data packets in Wireshark on the monitor interface?
>
> The following flags should all work with the brcm80211 FW:
>
> ? ? ? ?MCTL_KEEPBADFCS
> ? ? ? ?MCTL_KEEPCONTROL
> ? ? ? ?MCTL_PROMISC
> ? ? ? ?MCTL_BCNS_PROMISC
>
> The only one that's hooked up in the driver at the moment is
> MCTL_BCNS_PROMISC (for FIF_BCN_PRBRESP_PROMISC). ?I haven't taken a look at
> what it would take to enable monitor mode in the driver yet (setting up the
> monitor interface, etc).

For raw monitor mode, all but KEEPBADFCS are needed. If the "fcsfail"
monitor mode flag is also set, KEEPBADFCS should be enabled too.
For cooked monitor, AFAIK only KEEPCONTROL (and perhaps BCNS_PROMISC)
are needed.

However, do not set these based on interface type - use the FIF_ flags instead.

>
> - Henry
>
>



-- 
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)

  parent reply	other threads:[~2010-11-04 21:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04 12:21 pci id 14e4:4727 (bcm4313) status? Ariel Pedraza
2010-11-04 14:39 ` Gábor Stefanik
     [not found]   ` <4CD31B37.3000504@broadcom.com>
2010-11-04 21:42     ` Gábor Stefanik [this message]
2010-11-04 21:43       ` Gábor Stefanik
  -- strict thread matches above, loose matches on Subject: below --
2010-11-03 16:28 Jason
2010-11-03 16:35 ` Gábor Stefanik
2010-11-03 16:53 ` Larry Finger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=MjDUWSULLmVtRCdp2Hm6mDGe5Gw3D-XXKoakh@mail.gmail.com' \
    --to=netrolller.3d@gmail.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=henryp@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pedrazaa@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).