[Lxc-users] Problem with lxc and mutliple ips

[Andreas Laut]

Thanks Tamas and Guido for your help.
Dealing with stp options on the bridge wasn't a good option for us 
because we don't use a closed network solution and it could shutdown our 
provider net. (if they use stp too)

We figured out that interfaces starts smoother in lxc if we set 
lxc.network.hwaddr.
Sometimes an ip won't get configured for the first time but that repairs 
a arping or pinging the gateway inside container.


Regards,
Andreas


Am 11.10.2013 14:58, schrieb Tamas Papp:
> On 10/11/2013 02:42 PM, Andreas Laut wrote:
>> Hi,
>>
>> actually can't get lxc nightly compiled with debian right now,
>> configure has problems with pkg-config python3-dev (package pkg-config
>> and python3-dev is installed) (configure line 5588)
>>
>> I tried instead lxc 0.9 from tarball and got the same problem.
>>
>> Our LXC Config is attached, maybe this helps.
>> Our lxc-host bridge is configured like
>>
>> "auto br0
>> iface br0 inet static
>>          bridge_ports eth4
>>          bridge_stp off
>>          address 10.5.255.80
>>          netmask 255.255.0.0
>>          gateway 10.5.255.252"
> I used to add
>
>      bridge_fd 0
>      bridge_maxwait 0
>
>
> to the bridge config.
>
> tamas
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
> _______________________________________________
> Lxc-users mailing list
> Lxc-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lxc-users