From: "Stefanik Gábor" <netrolller.3d@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC 0/3] cfg80211, mac80211: Introduce radiotap flags for finer userspace control of injection
Date: Fri, 12 Dec 2008 23:54:03 +0100 [thread overview]
Message-ID: <69e28c910812121454t7d765b27l918e2f6162bd3f08@mail.gmail.com> (raw)
In-Reply-To: <1229122225.3565.16.camel@johannes.berg>
On Fri, Dec 12, 2008 at 11:50 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Fri, 2008-12-12 at 23:40 +0100, Stefanik G=E1bor wrote:
>
>> [...]
>
> Incidentally, as for the radiotap changes, I'm wondering whether the
> flag really should be "no seqno" or should be "assign seqno" instead.=
It
> seems injection should be "as raw as possible" by default. But things
> like that really need to be worked out with people from other systems=
=2E
>
> johannes
>
Using an "assign seqno" flag would cause existing injectors that
expect the kernel to do seq numbering for them to fail. This possibly
includes hostap and penumbra.
--=20
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-12-12 22:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 22:32 [RFC 0/3] cfg80211, mac80211: Introduce radiotap flags for finer userspace control of injection Stefanik Gábor
2008-12-12 22:37 ` Johannes Berg
2008-12-12 22:40 ` Stefanik Gábor
2008-12-12 22:42 ` Johannes Berg
2008-12-12 22:50 ` Johannes Berg
2008-12-12 22:54 ` Stefanik Gábor [this message]
2008-12-12 22:57 ` Johannes Berg
2008-12-13 0:20 ` Richard Farina
2008-12-13 0:26 ` 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=69e28c910812121454t7d765b27l918e2f6162bd3f08@mail.gmail.com \
--to=netrolller.3d@gmail.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