netdev - wireless vs. network namespaces

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-next>] [day] [month] [year] [list]

Message-Id: <1189763513.3974.26.camel@johannes.berg>
Date:	Fri, 14 Sep 2007 11:51:53 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	netdev <netdev@...r.kernel.org>,
	linux-wireless <linux-wireless@...r.kernel.org>
Subject: wireless vs. network namespaces

Now that the network namespace work is in net-2.6.24, I'm wondering how
wireless will be handling this. Is there any benefit at all to a
wireless device supporting network namespaces?

Should we, for now, set the new NETIF_F_NETNS_LOCAL flag for all
mac80211 devices?

If we do want to support moving, then we'll have to make cfg80211
(preferably, though mac80211 might be easier at first) migrate *all*
virtual interfaces associated with the same wiphy because otherwise
we'll get into trouble when moving one virtual interface and then
somebody in the other namespace changes its operating channel.

johannes

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