> > > >Yes, ultimately we'll need the physical device inside the same namespace > >as our application. Our application does a lot of management on the > >interface, > >monitoring things like the interface's link-pulse and such, and that > >wouldn't > >be available through a virtual interface. We can always redesign things > >to have the management portion run in the namespace with the physical > >interface, > >but for performance reasons we'd eventually want the physical interface to > >be > >directly inside the namespace anyway - so that would probably be wasted > >effort. > > > 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. Thanks, Chris _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
