From: Jiri Benc <jbenc@suse.cz>
To: Jiri Benc <jbenc@suse.cz>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [WIP] mac80211: kill mgmt interface
Date: Fri, 22 Jun 2007 15:45:45 +0200 [thread overview]
Message-ID: <20070622154545.29eeebdb@griffin.suse.cz> (raw)
In-Reply-To: <20070621151441.500d62d5@griffin.suse.cz>
On Thu, 21 Jun 2007 15:14:41 +0200, Jiri Benc wrote:
> That's true. Still, couldn't we find a better solution?
I have a new idea. Maybe it will turn out to have fatal design or
implementation problems, but anyway.
First, I thought how all of this would be easier if we have a native
802.11 (virtual) interfaces and don't translate from Ethernet. Then I
realized it wouldn't help us much - we want to specify some parameters
for each frame, so we'd have to use some encapsulation anyway to allow
radiotap headers. Hm, wait a moment - why we cannot use the
encapsulation we currently have? That means, why can't we encapsulate
raw 802.11 frames in Ethernet frames?
Before you reject the whole idea, please think a moment about it.
The actual implementation is not hard: use our own proprietary
ethertype and use the whole 802.11 frame including MAC and radiotap
header as a payload. We can even use the same format for sending
management frames to the user space for hostapd's use without any extra
interface.
Several things need to be handled first, of course:
- Returning of tx status. That could be solved by adding a stamp into
radiotap header of injected frame and returning a status (not the whole
frame, just the stamp plus some relevant info) through netlink.
- Interference with bridging. We don't want our injected (or returned
management) frame to be bridged. That could perhaps be solved by using
a certain Ethernet destination address (our own address?), but I'm not
sure here.
- There will probably more issues pop up.
Jiri
--
Jiri Benc
SUSE Labs
next prev parent reply other threads:[~2007-06-22 13:46 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 9:42 [WIP] mac80211: kill mgmt interface Johannes Berg
2007-06-21 12:35 ` Jiri Benc
2007-06-21 12:45 ` Johannes Berg
2007-06-21 13:14 ` Jiri Benc
2007-06-21 23:27 ` Andy Green
2007-06-22 13:45 ` Jiri Benc [this message]
2007-06-22 14:29 ` Andy Green
2007-06-22 15:30 ` Johannes Berg
2007-06-22 15:49 ` Jiri Benc
2007-06-22 20:20 ` Johannes Berg
2007-06-23 5:58 ` Andy Green
2007-06-23 6:53 ` Johannes Berg
2007-06-23 9:00 ` Andy Green
2007-06-23 21:48 ` Johannes Berg
2007-06-24 8:51 ` Andy Green
2007-06-24 9:38 ` Johannes Berg
2007-06-23 11:44 ` Jiri Benc
2007-06-23 12:23 ` Andy Green
2007-06-23 21:51 ` Johannes Berg
2007-06-24 8:39 ` Andy Green
2007-06-24 10:46 ` Jiri Benc
2007-06-22 15:39 ` Jiri Benc
2007-06-22 17:00 ` Andy Green
2007-06-23 8:29 ` Andy Green
2007-06-23 21:41 ` Johannes Berg
2007-06-21 13:35 ` Jouni Malinen
2007-06-22 5:05 ` Michael Wu
2007-06-22 10:12 ` Johannes Berg
2007-06-23 7:08 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2007-06-21 21:50 Joerg Pommnitz
2007-06-22 9:10 ` Johannes Berg
2007-06-22 13:15 ` Jiri Benc
2007-07-01 1:48 ` Cohen, Guy
2007-07-02 13:38 AW: " Joerg Pommnitz
2007-07-02 13:53 ` Jiri Benc
2007-07-04 6:13 ` Tomas Winkler
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=20070622154545.29eeebdb@griffin.suse.cz \
--to=jbenc@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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