From: Johannes Berg <johannes@sipsolutions.net>
To: Vadim Kochan <vadim4j@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH net-next] Allow to set net namespace for wireless device via RTM_LINK
Date: Mon, 12 Jan 2015 10:42:31 +0100 [thread overview]
Message-ID: <1421055751.1891.10.camel@sipsolutions.net> (raw)
In-Reply-To: <CAMw6YJJgPJw7jizR=Qe_2SOK=S0UKrm9AyE7MHUg1-wODEab2g@mail.gmail.com> (sfid-20150112_100748_746925_589D0E40)
On Mon, 2015-01-12 at 11:07 +0200, Vadim Kochan wrote:
> Would you please explain why wireless devs related to the same phy
> can't live in separated network namespaces ?
Well, they interact very deeply, for example the # of virtual interfaces
is often severely limited, and they often have to be using a single
channel, etc. It thus doesn't really make sense to try to separate them.
Also, if you really want to use it reliably, you should use a single
hostapd or wpa_supplicant process controlling all virtual interfaces,
which clearly isn't possible in multiple network namespaces.
johannes
next prev parent reply other threads:[~2015-01-12 9:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 20:35 [PATCH net-next] Allow to set net namespace for wireless device via RTM_LINK Vadim Kochan
2014-09-18 21:25 ` Johannes Berg
2014-09-18 21:25 ` Johannes Berg
2014-10-14 12:16 ` vadim4j
2014-10-20 9:47 ` Johannes Berg
2014-10-20 9:47 ` Johannes Berg
2014-10-20 10:46 ` Marcel Holtmann
2014-10-20 10:46 ` Marcel Holtmann
2014-10-20 10:52 ` Johannes Berg
2014-10-20 10:52 ` Johannes Berg
2014-12-24 9:48 ` Vadim Kochan
2015-01-05 9:22 ` Johannes Berg
2015-01-05 9:22 ` Johannes Berg
2015-01-12 9:07 ` Vadim Kochan
2015-01-12 9:42 ` Johannes Berg [this message]
2015-01-12 9:57 ` Vadim Kochan
2015-01-12 9:58 ` 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=1421055751.1891.10.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=vadim4j@gmail.com \
/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.