I have been experimenting with LXC virtualisation in order to run virtual machines on a dedicated server, but am having trouble setting up the networking properly.
I am using veth bridged networking, as instructed here: http://blog.foaa.de/2010/05/lxc-on-debian-squeeze/ (the guide I used to setup the LXC container)
When I start the container, it functions fine, can access the Internet and accepts incoming connections to it's own IP. However, as soon as I start it, the networking on my host box (dedicated server) goes down completely, and will not come back until the server is rebooted.
The only thing I can think of that would be causing this is incorrectly configured bridging settings, however I'm not sure entirely what the proper ones should be. Any advice on how I could reconfigure this? Thanks.
Both the host node and the container itself are running Debian Squeeze, with packages upgraded to the latest versions.
Host node (dedicated server) network configuration (/etc/network/interfaces):
allow-hotplug eth0 auto br0 iface br0 inet static bridge_ports eth0 bridge_fd 0 bridge_stp off bridge_maxwait 0 address 188.8.131.52 netmask 255.255.255.0 network 184.108.40.206 broadcast 220.127.116.11 gateway 18.104.22.168
LXC container network configuration (/etc/network/interfaces):
auto eth0 iface eth0 inet static address 22.214.171.124 netmask 255.255.255.0 broadcast 126.96.36.199 post-up route add 188.8.131.52 dev eth0 post-up route add default gw 184.108.40.206 post-down route del 220.127.116.11 dev eth0
Container network configuration (from LXC config file):
lxc.utsname = paradox lxc.network.type = veth lxc.network.flags = up lxc.network.link = br0 lxc.network.hwaddr = 02:00:00:ba:47:a0 lxc.network.ipv4 = 18.104.22.168