From: Kalle Valo <kvalo@adurom.com>
To: David Gnedt <david.gnedt@davizone.at>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
Grazvydas Ignotas <notasas@gmail.com>,
Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
Subject: Re: [PATCH 17/18] wl1251: enable tx path in monitor mode if necessary for packet injection
Date: Wed, 02 Feb 2011 00:47:13 +0200 [thread overview]
Message-ID: <87bp2vbcem.fsf@purkki.adurom.net> (raw)
In-Reply-To: <4D473F16.4010102@davizone.at> (David Gnedt's message of "Tue\, 01 Feb 2011 00\:00\:38 +0100")
David Gnedt <david.gnedt@davizone.at> writes:
> Am 2011-01-31 17:02, schrieb Kalle Valo:
>
>> I would like to step back and first look at the problem you are trying
>> to solve and maybe there's a way we can fix the join command. Was it
>> something to do with firmware sending extra frames? Unfortunately TI
>> firmwares are notorious for that.
>
> Yeah, you are right, but I don't think the JOIN command can be
> fixed. Even if we use it with a zero BSSID and zero SSID, it sends
> some frames.
What frames are we talking about exactly? (I can't test this right now.)
> All in all I think the JOIN command was only meant to be used when you really
> want to associate.
Yes, that has been my impression as well. But I really don't know if
we have any better options. Adding the hack you did to tx path is
really awkward as well.
> It would be really unpleasant if the firmware keeps sending frames
> while channel hopping (through user-space software) in monitor mode.
I don't see it as that bad really, but of course it depends what
frames are sent.
--
Kalle Valo
next prev parent reply other threads:[~2011-02-01 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D45A79A.1030102@davizone.at>
2011-01-30 19:11 ` [PATCH 17/18] wl1251: enable tx path in monitor mode if necessary for packet injection David Gnedt
2011-01-31 16:02 ` Kalle Valo
2011-01-31 23:00 ` David Gnedt
2011-02-01 22:47 ` Kalle Valo [this message]
2011-02-18 21:01 ` David Gnedt
2011-03-08 7:39 ` Kalle Valo
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=87bp2vbcem.fsf@purkki.adurom.net \
--to=kvalo@adurom.com \
--cc=GNUtoo@no-log.org \
--cc=david.gnedt@davizone.at \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=notasas@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.