[Lxc-users] Two virtual interfaces in a container

[Nirmal Guhan]

On Tue, Oct 19, 2010 at 3:03 PM, Serge E. Hallyn
<serge.hallyn at canonical.com> wrote:
> Quoting Serge E. Hallyn (serge.hallyn at canonical.com):
>> Quoting Nirmal Guhan (vavatutu at gmail.com):
>> > Hi,
>> >
>> > I have a requirement to create two virtual interfaces (eth0, eth1) in
>> > a linux container and separate traffic between the two based on ip
>> > route. Basically eth0 (or eth1) should be used for external world and
>> > eth1 for communication terminating at host. How do I go about doing
>> > this?
>> >
>> > I created two interfaces in the config and can see both of them in the
>> > container.
>> >
>> > lxc.network.type = veth
>> > lxc.network.link = br0
>> > lxc.network.ipv4 = 128.107.159.183/22
>> > lxc.network.name = eth0
>> > lxc.network.flags = up
>> > lxc.network.mtu = 1500
>> > lxc.network.type = veth
>> > lxc.network.link = br0
>>
>> If you want eth1 to be connected internally only, then shouldn't
>> you create a bridge br1, and use that here?  Don't connect br1
>> to the physical nic, and you'll have your host-only bridge.

Ok. This is what I did.
#brctl addbr br1

Modified above config to lxc.network.link=br1 for eth1 and removed
eth0 so there is only one i/f. Since br1 is not attached to nic, how
do I now test host<->guest communication.Obviously I can't reach eth0
ip from lxc.
>
> (BTW, I assume that the reason you failed to ping then was that
> your eth1 in the container had an address on a different subnet,
> and - I assume - there was no route known on the host to that
> subnet.  I could be wrong, but since your test seemed to be
> unrelated to your end goal I thought I'd comment first on how
> to do what you want)
It is in same subnet. I think it was to do with ip route setup.

--Nirmal

>
> -serge
>