From: Andy Green <andy@warmcat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: radiotap injection bugs & extending it
Date: Sat, 01 Sep 2007 10:21:00 +0100 [thread overview]
Message-ID: <46D92EFC.2060007@warmcat.com> (raw)
In-Reply-To: <1188637615.7585.118.camel@johannes.berg>
Somebody in the thread at some point said:
> On Sat, 2007-09-01 at 10:00 +0100, Andy Green wrote:
>
>> Yes it's wrong, hdr is also dereferenced once more while the radiotap
>> header is still in place. I made a little patch I will send in a
>> moment, if you already did it then ignore the patch.
>
> No, sent the mail just before going to sleep :) I'll review your patch
> and adopt it. Guess I get to rebase my ~70ish patches to after it
> then ;)
Hopefully it's just fuzz...
>>> Also, after doing more work on mac80211 I now again have hostapd running
>>> via monitor interfaces. However, there's a bit of a problem there.
>> You are definitely on fire at the moment Johannes.
>
> Heh, yeah, got a bit of time on my hands right now.
Opposite for me, having to do paying work at the moment.
> Yeah, I can do that. Not sure about PS mode though. I suppose your use
> case won't suffer if I simply do it unconditionally since you're always
> sending multicast frames anyhow.
Well because our frames aren't targeted at any real MAC I'm not sure the
AP will buffer them for devices in PS or not. Maybe the client having
an interface up in hardware promisc should be a sign for it to not go
into PS mode anyway?
For sure things will be much better and more consistent if we can inject
down unassociated interfaces reliably, so this is a nice move.
>>> This is basically it, except for short preamble setting. That is a bit
>>> of a problem, however, because it's not a tristate in radiotap and we
>>> want a tristate (long/short/automatic). Ideas on this item?
>> No idea about it here.
>
> I could propose adding a new radiotap TX flag, I suppose...
I don't know enough about it to have a proper idea, sorry.
-Andy
next prev parent reply other threads:[~2007-09-01 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-01 1:12 radiotap injection bugs & extending it Johannes Berg
2007-09-01 9:00 ` Andy Green
2007-09-01 9:06 ` Johannes Berg
2007-09-01 9:21 ` Andy Green [this message]
2007-09-01 9:36 ` Johannes Berg
2007-09-01 9:47 ` Andy Green
2007-09-01 9:55 ` Johannes Berg
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=46D92EFC.2060007@warmcat.com \
--to=andy@warmcat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).