On Thu, Jan 15, 2009 at 11:21:43PM +0100, Daniel Lezcano wrote: > chris@xxxxxxxxxxxxx wrote: > >>Did you tried with the macvlan ? > >> > > > >I just tried it - and it does work - I can move the vlan interfaces into > >the > >namespace. But that's not a solution for us - we really need to support > >communications out to other nodes on the network that we can't count on > >using > >vlan. > > > Perhaps I am misunderstand but the macvlan is just an "eth aliased" > interface, so you should but able to communicate with the outside world > and keep the same performances as the physical device, no ? The only > drawback with the macvlan is you can not communicate on the same host > between different namespaces. We did some benchmark last year wih the > macvlan and we got very good results. Oh great, I confused the macvlan support with 802.1q vlan interfaces (as added through vconfig). macvlan does look very promising - I was able to create a macvlan interface and assign it to my namespace - looks pretty good! Thanks, Chris _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
