From: David Gnedt <david.gnedt@davizone.at>
To: Kalle Valo <kvalo@adurom.com>
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: Fri, 18 Feb 2011 22:01:02 +0100 [thread overview]
Message-ID: <4D5EDE0E.9060004@davizone.at> (raw)
In-Reply-To: <87bp2vbcem.fsf@purkki.adurom.net>
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
Am 2011-02-01 23:47, schrieb Kalle Valo:
> What frames are we talking about exactly? (I can't test this right now.)
They look to me like CTS-to-Self frames. I have attached a sample of them. There
is no other RTS/CTS traffic on the same channel.
I have done further testing for channel switching in monitor mode and there are
some promising results. It looks like the CTS-to-self frames are not sent if
JOIN is used as usual but DISABLE_TX is issued first. Moreover the TX path
remains enabled with this combination.
I thought it would be best to implement it in the following way:
Start with disabled TX path. I found that enabling TX path at least once is
necessary, so it will be ENABLE_TX followed by DISABLE_TX.
It looks to me like managed mode also works after DISABLE_TX, but just to be
sure I will add a ENABLE_TX in wl1251_op_add_interface and a DISABLE_TX in
wl1251_op_remove_interface.
You can find the complete results here: http://wiki.maemo.org/Wl1251/Development
[-- Attachment #2: wl1251_join_cts_frames.cap --]
[-- Type: application/cap, Size: 148 bytes --]
next prev parent reply other threads:[~2011-02-18 21:01 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
2011-02-18 21:01 ` David Gnedt [this message]
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=4D5EDE0E.9060004@davizone.at \
--to=david.gnedt@davizone.at \
--cc=GNUtoo@no-log.org \
--cc=kvalo@adurom.com \
--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.