From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
netdev <netdev@vger.kernel.org>, Jouni Malinen <j@w1.fi>
Subject: Re: wireless vs. network namespaces (part II)
Date: Mon, 29 Sep 2008 12:03:45 -0700 [thread overview]
Message-ID: <20080929190345.GD6203@tesla> (raw)
In-Reply-To: <1222587651.3798.72.camel@johannes.berg>
On Sun, Sep 28, 2008 at 12:40:51AM -0700, Johannes Berg wrote:
> On Sat, 2008-09-27 at 18:39 -0700, Eric W. Biederman wrote:
> > In the wired ethernet world there is a lot of value in moving just
> > a vlan interface or just one mac address with mac vlan into a network
> > namespace. Allowing full speed access to the hardware that can do
> > just about anything while functionally restricting what user space
> > can do with the hardware.
>
> Right, except that wireless really is different in that for one you
> can't really usefully have multiple virtual interfaces unless you're
> making an AP
Well it may be possible later in STA too, but that is just me looking at
a crystal ball.
> (and I think it's unlikely you'd want that in an AP, and
> even if I'm not willing to support it,
You mean AP VLANs? I thought you added that code already. I don't
follow.
Luis
next prev parent reply other threads:[~2008-09-29 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-27 10:01 wireless vs. network namespaces (part II) Johannes Berg
[not found] ` <1222509685.3798.59.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-09-28 1:39 ` Eric W. Biederman
2008-09-28 7:40 ` Johannes Berg
2008-09-29 5:44 ` Eric W. Biederman
2008-09-29 8:19 ` Johannes Berg
2008-09-29 19:03 ` Luis R. Rodriguez [this message]
2008-09-29 19:05 ` 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=20080929190345.GD6203@tesla \
--to=lrodriguez@atheros.com \
--cc=ebiederm@xmission.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).