Thanks Fajar. Atlast I got the vlan thingy working
I added 2 vlans to eth0 (eth0.211 and eth0.103) and connected them to
bridge br0 and used br0 as a link to container(veth)
To reach the host I used another interface eth1(probably assigning ip to
bridge br0 would have solved that problem)
i should give openvswitch a try. Thanks for the link
On Wed, Oct 31, 2012 at 9:39 AM, Fajar A. Nugraha <l...@fajar.net> wrote:
> On Wed, Oct 31, 2012 at 12:39 AM, brian mullan <bmullan.m...@gmail.com>
> wrote:
> > Kalyana & Fajar
> >
> > I know this answer isn't about VLAN specifically but it might interest
> you.
> > I'd stumbled upon it a few weeks ago and the title was
> > "Connecting containers on several hosts with Open vSwitch"
> >
> >
> http://s3hh.wordpress.com/2012/05/28/connecting-containers-on-several-hosts-with-open-vswitch/
> >
> > There was also a newer post regarding Open vSwitch and LXC:
> > http://s3hh.wordpress.com/
>
>
> Last time I tested, openvswicth is more powerful, but kinda
> complicated for new users who are used to linux bridge.
>
> Anyway, back to Kalyana's requirement, you can either:
> - bridge the trunk (eth0) to the container, and create vlan on the
> interface in container side (i.e. create eth0.100 in the container)
> - bridge the vlan interface (eth0.100) to the container, and use the
> interface on container side (eth0) directly as regular interface
>
> --
> Fajar
>
--
Kalyanasundaram
http://blogs.eskratch.com/
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users
