From: Bruno Randolf <br1@einfach.org>
To: Michael Stahn <m1kes@web.de>
Cc: linux-wireless@vger.kernel.org,
"Gábor Stefanik" <netrolller.3d@gmail.com>,
"Jouni Malinen" <j@w1.fi>
Subject: Re: [Proposal]TX flags
Date: Wed, 24 Mar 2010 20:15:21 +0900 [thread overview]
Message-ID: <201003242015.21409.br1@einfach.org> (raw)
In-Reply-To: <loom.20100323T162144-640@post.gmane.org>
On Wednesday 24 March 2010 00:50:31 Michael Stahn wrote:
> > similar to this we would also need to be able to specify that the beacon
> > TSF should not be overwritten. maybe a general flag like "do not change"
> > would do?
>
> Is TSF really overwritten at manual injection from userspace?
Yes, it is, at least on ath5k. And as jouni has pointed out recently this
behaviour is expected by hostapd (maybe not for beacons but for probe
request/response frames, i dont know).
Gabor Stefanik proposed a while ago that frames should only be modified by the
driver in cooked monitor mode (COOK_FRAMES), that way we could avoid defining
new radiotap flags. What's your view on that, Jouni?
bruno
next prev parent reply other threads:[~2010-03-24 11:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 0:33 [Proposal]TX flags Gábor Stefanik
2009-04-16 15:37 ` David Young
2009-04-16 17:28 ` Johannes Berg
2009-04-16 18:47 ` Gábor Stefanik
2009-04-16 18:59 ` Johannes Berg
2009-04-16 19:10 ` Michael Buesch
2009-04-16 20:48 ` David Young
2009-04-17 1:24 ` Gábor Stefanik
2009-04-17 9:50 ` Johannes Berg
2009-04-16 20:33 ` David Young
2009-04-16 20:48 ` Johannes Berg
2010-03-22 19:32 ` Michael Stahn
2010-03-23 0:42 ` Bruno Randolf
2010-03-23 15:50 ` Michael Stahn
2010-03-24 11:15 ` Bruno Randolf [this message]
2010-03-24 19:43 ` Pavel Roskin
2010-03-24 20:26 ` Gábor Stefanik
2010-03-25 1:22 ` Michael Stahn
2010-03-25 20:32 ` Gábor Stefanik
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=201003242015.21409.br1@einfach.org \
--to=br1@einfach.org \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=m1kes@web.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;
as well as URLs for NNTP newsgroup(s).