[lxc-devel] lxc.network.type = macvlan

[jorge espada]

The error was  ICMP "no route to host", but now i change the conf and
instead of vepa I used bridge...after destroy and create the containers with
the new conf, seems to be working as expected for a while, but from time to
time "the container became unresponsive".. no ping (100% packet lost). The
curious thing is, if I login into the host and then to the container
(lxc-console) and ping another container or host the " unresponsive
container " become alive again (ping OK)....so I'm a bit lost..

Jorge E. Espada



On Wed, Oct 13, 2010 at 2:17 AM, Daniel Lezcano <dlezcano at fr.ibm.com> wrote:

> On 10/12/2010 10:29 PM, jorge espada wrote:
>
>> Hi, I have a lxc container  running on debian lenny (kernel 2.6.32) with
>> the
>> following conf:
>>
>> lxc.network.type = macvlan
>> lxc.network.flags = up
>> lxc.network.link = vlan310
>> lxc.network.name = vlan310
>> lxc.network.macvlan.mode = vepa
>> lxc.network.hwaddr = 06:00:0a:1f:00:46
>> lxc.network.ipv4 = 10.31.0.70/24
>>
>> # network2
>> lxc.network.type = macvlan
>> lxc.network.flags = up
>> lxc.network.link = vlan400
>> lxc.network.name = vlan400
>> lxc.network.macvlan.mode = vepa
>> lxc.network.hwaddr = 06:00:0a:28:00:46
>> lxc.network.ipv4 = 10.40.0.70/23
>>
>>
>> is the macvlan mode vepa supported for that kernel or I need a newer one?
>>
>
> You need a 2.6.33 kernel version.
>
>
>  Because I have weird problems with that conf, some times I can ping the
>> container from another host but some times not...is random
>>
>
> I am not sure it is related. What happens when you can't ping the host ?
> What is the error ? ICMP "no route to host" ? or just the packet are lost ?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-devel/attachments/20101013/9d2d0728/attachment.html>