linux-kernel - Re: Cannot put ath9k interface to different namespace?

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]

Date:	Sat, 18 Feb 2012 23:52:52 +0100
From:	Johannes Berg <johannes@...solutions.net>
To:	Michael Leun <lkml20120218@...ton.leun.net>,
	linux-wireless@...r.kernel.org, ath9k-devel@...ts.ath9k.org
CC:	mcgrof@....qualcomm.com, jouni@....qualcomm.com,
	vthiagar@....qualcomm.com, senthilb@....qualcomm.com,
	linux-kernel@...r.kernel.org
Subject: Re: Cannot put ath9k interface to different namespace?

You have to put the entire wiphy into the netns with iw, not just one virtual interface. 

Michael Leun <lkml20120218@...ton.leun.net> wrote:

>Hi,
>
>tried to put ath9k_htc interface to namespace, does not work:
>
>jill:/home/ml # ip link set netns 4001 dev wlan3
>RTNETLINK answers: Invalid argument
>
>Also does not work with ath9k, but does work with other wlan devices
>(tried zd1201, r8712u, thats what I've here at the moment).
>
>When trying, device was down.
>
>Is there some trick to do it or is there some support from driver for
>that missing?
>
>Any plans to fix that? Would that be big effort?
>
>Thanks.
>
>-- 
>MfG,
>
>Michael Leun
>
>--
>To unsubscribe from this list: send the line "unsubscribe
>linux-wireless" in
>the body of a message to majordomo@...r.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Sent from my tablet. Please excuse my brevity.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/