[lxc-devel] lxc-stop/start drops other lxc network connections
Is there any reason why I'm seeing other lxc's drop their network connections when I stop or start another lxc? I'm running a bridging network with static ip's on lxc's, see below. This is happening on both Ubuntu pkgs: 0.7.4-0ubuntu7.3 & 0.7.5-3ubuntu59. Any advice would be greatly appreciated. --- /etc/network/interfaces --- auto br0 iface br0 inet static address 192.168.0.1 network 192.168.0.0 netmask 255.255.252.0 broadcast 192.168.3.255 bridge_maxwait 5 bridge_fd 0 pre-up /usr/sbin/brctl addbr br0 -- --- dmesg output - [6636083.276750] eth0: no IPv6 routers present [6636083.356606] vethQmGcj9: no IPv6 routers present [6636087.549377] br0: port 3(vethQmGcj9) entering forwarding state [6636876.087425] br0: port 3(vethQmGcj9) entering forwarding state [6636876.180172] br0: port 3(vethQmGcj9) entering disabled state [6636978.696950] device vethdkxmWu entered promiscuous mode [6636978.698854] ADDRCONF(NETDEV_UP): vethdkxmWu: link is not ready [6636979.087122] ADDRCONF(NETDEV_CHANGE): vethdkxmWu: link becomes ready [6636979.087177] br0: port 3(vethdkxmWu) entering learning state [6636979.087181] br0: port 3(vethdkxmWu) entering learning state [6636989.273244] vethdkxmWu: no IPv6 routers present [6636989.592703] eth0: no IPv6 routers present [6636994.094936] br0: port 3(vethdkxmWu) entering forwarding state -- -- sample lxc.conf - lxc.utsname = lxc-7 lxc.tty = 4 lxc.pts = 1024 lxc.network.type = veth lxc.network.flags = up lxc.network.link = br0 lxc.network.name = eth0 lxc.network.mtu = 1500 lxc.network.ipv4 = 192.168.1.7/22 lxc.rootfs = /lxc-7/rootfs lxc.cgroup.cpuset.cpus = 14-15 lxc.cgroup.memory.limit_in_bytes = 8G lxc.cgroup.devices.deny = a lxc.cgroup.devices.allow = c 1:3 rwm lxc.cgroup.devices.allow = c 1:5 rwm lxc.cgroup.devices.allow = c 5:1 rwm lxc.cgroup.devices.allow = c 5:0 rwm lxc.cgroup.devices.allow = c 4:0 rwm lxc.cgroup.devices.allow = c 4:1 rwm lxc.cgroup.devices.allow = c 1:9 rwm lxc.cgroup.devices.allow = c 1:8 rwm lxc.cgroup.devices.allow = c 136:* rwm lxc.cgroup.devices.allow = c 5:2 rwm lxc.cgroup.devices.allow = c 254:0 rwm - Thanks, Dusty -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
Re: [lxc-devel] lxc-stop/start drops other lxc network connections
Guido, Thanks for the info and link. It appears that is the issue. I had problems manually setting the br0 hw address so I incremented it and added it to the lxc configuration. IE: br0 -> 02:35:0c:76:ad:cd lxc0.conf: lxc.network.hwaddr = 02:35:0c:76:ae:00 Thanks, On Mon, Sep 10, 2012 at 2:10 AM, Jäkel, Guido wrote: > Dear Dusty, > > might be the well-known issue concerning the MAC of a bridge and the attached > interfaces (here: veth's): If the MAC of the bridge isn't lower than the MAC > of all of it's attached devices, the "outer world" will see a MAC change on > plumbing this interface (see e.g. > http://sourceforge.net/tracker/?func=detail&aid=3411497&group_id=163076&atid=826303). > > Assign either a "very low" MAC to the bridge or "very high" MACs to the > containers interface via the lxc.network.hwaddr property. > > Greetings > > Guido -- Dusty -- How fast is your code? 3 out of 4 devs don\\\'t know how their code performs in production. Find out how slow your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219672;13503038;z? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
