Daniel Smith (2011-11-21 08:12:16 -0500) wrote: > On 11/21/2011 7:20 AM, Ivan Vilata i Balaguer wrote: > > Hi all. I'm having trouble moving a physical, unused WiFi interface in my > > computer to a container, which uses a network configuration like this:: > > So I ran into the problem as well, what I found was that the whole wiphy > had to be moved over into the namespace manually with the iw command. > After which you have to use the iw command again inside the container to > create a new interface. A word of caution, I have found even though > the phy is in another namespace you can still add vifs to it. Even > though it is possible, don't! It will hang your system when you shutdown > the container(s). > > Hope this helps.
Indeed it does, thanks! I didn't need to run iw under the container, it appeared there instantly after moving the interface from the host. I don't know what you mean by adding vifs to the moved interface, but thanks for the advice. :) However, I think this should be automatically set up by the "lxc.network.type = phys" option, so if no one has a clear reason of why this isn't supported I'll file a new issue in the tracker. Cheers, -- Ivan Vilata i Balaguer -- https://elvil.net/ ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
