From: Andy Green <andy@warmcat.com>
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: Sat, 23 Jun 2007 13:23:22 +0100 [thread overview]
Message-ID: <467D10BA.80104@warmcat.com> (raw)
In-Reply-To: <20070623134451.643dd40c@logostar.upir.cz>
Jiri Benc wrote:
> On Sat, 23 Jun 2007 08:53:50 +0200, Johannes Berg wrote:
>> Who started this anti-nl80211 thing anyway? I still don't see what's so
>> wrong with sending frames down a PF_NETLINK socket rather than a
>> PF_PACKET socket.
>
> Perhaps it was just my misunderstanding about the monitor interface tx
> injection patches; I though this mechanism should be used for hostapd and
> user space MLME, which I consider wrong. Johannes' comment about different
> needs (and thus having both injection through monitor iface and through
> netlink) makes perfectly sense, though.
>
> Andy, is using a monitor interface (for both injecting and receiving of
> frames) acceptable for you? If yes, let's drop my proposal (I said it might
> turn up to be useless :-)), apply patches for monitor iface injection and
> implement a netlink soultion as a replacement of the current management
> interface.
Yes the existing Monitor Mode Try #13 is fine for me and the userland
projects I know about, but actually I quite liked your encapsulation
thing -- in itself is compatible with working in any mode. The only
problem with it right now is that it seems when mananged mode interfaces
are not associated, they are in a netif_carrier_off() state or similar.
If in the future it becomes possible to via netlink to target types of
packets to come down any interface in encapsulated bubbles, then
possibly it makes sense to use the encapsulated version. But of course
either way will be great compared to nothing.
-Andy
next prev parent reply other threads:[~2007-06-23 12:23 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
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 [this message]
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=467D10BA.80104@warmcat.com \
--to=andy@warmcat.com \
--cc=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 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.