netdev - Re: wireless vs. network namespaces (part II)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1222715153.7064.42.camel@johannes.berg>
Date:	Mon, 29 Sep 2008 21:05:53 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	"Luis R. Rodriguez" <lrodriguez@...eros.com>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	linux-wireless <linux-wireless@...r.kernel.org>,
	netdev <netdev@...r.kernel.org>, Jouni Malinen <j@...fi>
Subject: Re: wireless vs. network namespaces (part II)

On Mon, 2008-09-29 at 12:03 -0700, Luis R. Rodriguez wrote:

> > 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.

Well, it _is_ possible, but not standards compliant ;) Stefano is, I
think, the only person who has ever tested my firmware patch.

> > (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.

Well, I don't see a point in allowing them in different network
namespaces.

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)