/etc/network/interfaces.tail is ignored on Debian appliance

[Comune di Levico Terme]

Hi, i have a problem with a configuration of network in a OpenVZ virtual machine.

I'm using this template: debian-5.0-standard_5.0-2_i386.tar.gz

This is my proxmox version: pveversion -v
pve-manager: 1.5-7 (pve-manager/1.5/4660)
running kernel: 2.6.24-8-pve
pve-kernel-2.6.24-8-pve: 2.6.24-16
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1

I read that from the proxmox 1.5 i should not edit /etc/network/interfaces directly but I should create an interfaces.tail or an interfaces.head instead.

I tried that, 2 or 3 weeks ago, and everything was ok.
2 days ago, i make an apt-get update and an apt-get upgrade.

Now i must edit directly the /etc/network/interfaces because proxmox (or the OpenVZ container... i don't know) ignores the interfaces.tail and interfaces.head

On the web interface in the "status tab" of the virtual machine the value "IP address" is the value "unknown" ... it's normal ?

There is a better way to configure the network cards for the machines openvz ?

thank you... and sorry for my english !

 

[tom]

do you use venet or veth? if you use veth the value "unknown" is ok, as the host does not see the IP from the guest.

 

[Comune di Levico Terme]

I'm using veth.

 

[tom]

if possible, use venet.
see the differences: http://wiki.openvz.org/Differences_between_venet_and_veth

if you need veth, the network configuration needs to be done inside the guest - the same way as you would configure it on a physical host.

 

[dietmar]

I tried that, 2 or 3 weeks ago, and everything was ok.
2 days ago, i make an apt-get update and an apt-get upgrade.

We had a serious bug 2 weeks ago, and we fixed that now. /etc/network/interfaces is not touched when you use veth.

 

[Comune di Levico Terme]

Thank you Tom for your reply.

I think that I can't use a venet in my specific case:
- I have a server with 2 network interface
- the first is for network lan (192.168.32.x with a GW 192.168.32.250)
- the second is for a DMZ (192.168.40.x with a GW 192.168.32.250)
- i use Shorewall for manage traffic on my Proxmox
- when I configure a veth i can use it in my shorewall configuration (for example: veth201.0)
- when I configure a venet can I identify the single network for use in Shorewall configuration ?

 

[Comune di Levico Terme]

OK, Thank you very much for your reply.