<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hey,<br><br>i'm doing a few tests with migrating ovz containers to lxc. Learning about advantages and disadvantages of both.<br>Here are the instructions that i use to convert the containers: <a href="https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC" target="_blank">https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC</a><br>The main point that i struggle is to switch from venets to the eths of lxc.<br><br>Running the container with one eth0 and one ip works perfect. But with a second interface eth1 and a second ip there is some routing problem. The second ip is not pingable from outside.<br>I'm using precreated images from here <cite class="_Rm"><a href="https://wiki.openvz.org/Download/template/precreated" target="_blank">https://wiki.openvz.org/Download/template/precreated</a> (Ubuntu 12.04 and Ubuntu 14.04)<br><br>interfaces inside the container:<br></cite>auto eth0<br>iface eth0 inet static<br><pre> address xx.xx.xx.xx<br> netmask 255.255.255.255<br># --- BEGIN PVE ---<br> post-up ip route add xx.xx.xx.254 dev eth0<br> post-up ip route add default via xx.xx.xx.254 dev eth0<br> pre-down ip route del default via xx.xx.xx.254 dev eth0<br> pre-down ip route del xx.xx.xx.254 dev eth0<br># --- END PVE ---<br>auto eth1 <br>iface eth1 inet static<br> address xx.xx.xx.xx<br> netmask 255.255.255.255<br> </pre>Original templates from lxc don't have that problem. My question - is there any setting inside the container template that forbids the routing to eth1?<br><br>Thank you, chris<br> </div></body>
</html>