From: Johannes Berg <johannes@sipsolutions.net>
To: "Stefanik Gábor" <netrolller.3d@gmail.com>
Cc: "bcm43xx-dev@lists.berlios.de" <bcm43xx-dev@lists.berlios.de>,
Michael Buesch <mb@bu3sch.de>,
Larry Finger <Larry.Finger@lwfinger.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: BUG(?): dev->wl->if_type is 0 for monitor interfaces (should be 5); b43_is_mode(dev->wl; IEEE80211_IF_TYPE_MNTR) is always false
Date: Wed, 25 Jun 2008 22:26:30 +0200 [thread overview]
Message-ID: <1214425590.21847.61.camel@johannes.berg> (raw)
In-Reply-To: <69e28c910806251323j3a80b31etde8683d573dcf2fa@mail.gmail.com> (sfid-20080625_222356_890423_579F588A)
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
On Wed, 2008-06-25 at 22:23 +0200, Stefanik Gábor wrote:
> On Wed, Jun 25, 2008 at 10:22 PM, Stefanik Gábor
> <netrolller.3d@gmail.com> wrote:
> > In both b43 and b43legacy, dev->wl->if_type is 0
> > (IEEE80211_IF_TYPE_INVALID) when injecting/transmitting packets on a
> > monitor interface (not sure about receiving), while the logical result
> > would be 5 (IEEE80211_IF_TYPE_MNTR).
I should answer on the list too then:
No, 5 wouldn't be the logical result. Try to understand how monitor mode
and virtual interfaces in mac80211 work.
b43 only sees what mode it is operating in, but pure monitor mode isn't
"operating" at all.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2008-06-25 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <69e28c910806251322i31a8cb4flc7b6c85e8884a5ca@mail.gmail.com>
2008-06-25 20:23 ` BUG(?): dev->wl->if_type is 0 for monitor interfaces (should be 5); b43_is_mode(dev->wl; IEEE80211_IF_TYPE_MNTR) is always false Stefanik Gábor
2008-06-25 20:26 ` Johannes Berg [this message]
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=1214425590.21847.61.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=netrolller.3d@gmail.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