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

[jorge espada]

My bad guys, it was a route problem...i have 3 vlans for each container and
also 3 default gw in /etc/network/interfaces (copy and paste :S )...and no
custom route...so...
I modified the conf in /etc/network/interfaces and solved the problem.
Thanks

Jorge E. Espada



On Thu, Oct 14, 2010 at 11:40 AM, jorge espada <espada.jorge at gmail.com>wrote:

> As extra information  I have configured a bonding in the host(where the
> container is running) and the vlans over it:
> auto bond0
> iface bond0 inet manual
>         up /sbin/ifconfig bond0 up
>         down /sbin/ifconfig bond0 down
>         slaves eth0 eth1
>         bond_mode balance-xor
>         bond_miimon 100
>         bond_updelay 200
>         bond_downdelay 200
>
> auto vlan310
> iface vlan310 inet static
>         address 10.31.0.151
>         netmask 255.255.255.0
>         network 10.31.0.0
>         broadcast 10.31.0.255
>         gateway 10.31.0.1
>         vlan_raw_device bond0
>
>
> Jorge E. Espada
>
>
>
>
> On Wed, Oct 13, 2010 at 10:06 AM, jorge espada <espada.jorge at gmail.com>wrote:
>
>> No, from the host:
>>
>> Oct 10 06:25:01 srvc15 kernel: imklog 4.4.2, log source = /proc/kmsg
>> started.
>> Oct 10 06:25:01 srvc15 rsyslogd: [origin software="rsyslogd"
>> swVersion="4.4.2" x-pid="2075" x-info="http://www.rsyslog.com"] (re)start
>> Oct 11 06:25:01 srvc15 rsyslogd: [origin software="rsyslogd"
>> swVersion="4.4.2" x-pid="2075" x-info="http://www.rsyslog.com"] rsyslogd
>> was HUPed, type 'restart'.
>> Oct 11 06:25:01 srvc15 kernel: imklog 4.4.2, log source = /proc/kmsg
>> started.
>> Oct 11 06:25:01 srvc15 rsyslogd: [origin software="rsyslogd"
>> swVersion="4.4.2" x-pid="2075" x-info="http://www.rsyslog.com"] (re)start
>> Oct 12 06:25:01 srvc15 rsyslogd: [origin software="rsyslogd"
>> swVersion="4.4.2" x-pid="2075" x-info="http://www.rsyslog.com"] rsyslogd
>> was HUPed, type 'restart'.
>> Oct 12 06:25:01 srvc15 kernel: Kernel logging (proc) stopped.
>> Oct 12 06:25:01 srvc15 kernel: imklog 4.4.2, log source = /proc/kmsg
>> started.
>> Oct 12 06:25:01 srvc15 rsyslogd: [origin software="rsyslogd"
>> swVersion="4.4.2" x-pid="2075" x-info="http://www.rsyslog.com"] (re)start
>> Oct 13 06:25:01 srvc15 rsyslogd: [origin software="rsyslogd"
>> swVersion="4.4.2" x-pid="2075" x-info="http://www.rsyslog.com"] rsyslogd
>> was HUPed, type 'restart'.
>> Oct 13 06:25:01 srvc15 kernel: Kernel logging (proc) stopped.
>> Oct 13 06:25:01 srvc15 kernel: imklog 4.4.2, log source = /proc/kmsg
>> started.
>> Oct 13 06:25:01 srvc15 rsyslogd: [origin software="rsyslogd"
>> swVersion="4.4.2" x-pid="2075" x-info="http://www.rsyslog.com"] (re)start
>>
>> From the container:
>> Oct 10 06:25:01 srvc15c0 kernel: imklog 3.18.6, log source = /proc/kmsg
>> started.
>> Oct 10 06:25:01 srvc15c0 rsyslogd: [origin software="rsyslogd"
>> swVersion="3.18.6" x-pid="299" x-info="http://www.rsyslog.com"] restart
>> Oct 11 06:25:01 srvc15c0 kernel: imklog 3.18.6, log source = /proc/kmsg
>> started.
>> Oct 11 06:25:01 srvc15c0 rsyslogd: [origin software="rsyslogd"
>> swVersion="3.18.6" x-pid="299" x-info="http://www.rsyslog.com"] restart
>> Oct 12 06:25:01 srvc15c0 kernel: imklog 3.18.6, log source = /proc/kmsg
>> started.
>> Oct 12 06:25:01 srvc15c0 rsyslogd: [origin software="rsyslogd"
>> swVersion="3.18.6" x-pid="299" x-info="http://www.rsyslog.com"] restart
>> Oct 13 06:25:01 srvc15c0 kernel: imklog 3.18.6, log source = /proc/kmsg
>> started.
>> Oct 13 06:25:01 srvc15c0 rsyslogd: [origin software="rsyslogd"
>> swVersion="3.18.6" x-pid="299" x-info="http://www.rsyslog.com"] restart
>>
>> That's all :(
>> Jorge E. Espada
>>
>>
>>
>>
>> On Wed, Oct 13, 2010 at 9:45 AM, Daniel Lezcano <dlezcano at fr.ibm.com>wrote:
>>
>>> On 10/13/2010 02:42 PM, jorge espada wrote:
>>>
>>>> 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..
>>>>
>>>
>>> Is there any trace in /var/log/messages ?
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-devel/attachments/20101020/2a107eb6/attachment.html>