Hi,
I am working in an environment where I have multiple systems each having four
wireless devices (ath9k) and would like to run four containers each with a wlan
device bound/dedicated to that container. The driving requirements that I am
trying to meet is first the traffic entering the wireless infrastructure must
appear to originate from the container, preferably without any intermediary L3
hops. Second is that inter-container traffic on the same device must traverse
the wireless network infrastructure and not directly through the local kernel's
network stack. I did an initial attempt using a phys link type with the link
being the wlan0 device, but when I tried this using a 2.6.37 kernel lxc
complained the network was not properly configured. So the options I have been
weighing are the following,
- Confirm wlan device cannot be used for a phys link type.
- See if macvlan could be used with an ath9k wireless device and that
the resulting macvlan{n} device can be used as a phys link.
- Create a private bridge with veth, for the container, and wlan{n}
attached
- Create a bridge for the container and the use iptables to nat the
traffic onto the wlan device.
The last option I know will work but the results are the least desirable in
meeting the requirements and has the added complexity/overhead of having to
manage netfilter rules for all the systems. So any help, advice, alternative
solutions, or similar experience would be greatly appreciated.
V/r,
Daniel P. Smith
------------------------------------------------------------------------------
Fulfilling the Lean Software Promise
Lean software platforms are now widely adopted and the benefits have been
demonstrated beyond question. Learn why your peers are replacing JEE
containers with lightweight application servers - and what you can gain
from the move. http://p.sf.net/sfu/vmware-sfemails
_______________________________________________
Lxc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lxc-users
