Hi
well, I rebooted some hardware-nodes to get the latest 2.6.32-6-pve kernel to work.
The problem that arises is now that ipv6 shows up in the VE though it is a system based on debian-3.1 template (which should normally prevent the script to inject v6 configurations in /etc/network/interfaces).
And the much bigger problem is the assumption that seems to be made about the IP that is added to this VE:
auto venet0:0
iface venet0:0 inet static
address 10.116.5.1
netmask 255.255.255.0
broadcast 0.0.0.0
because we never configured a /24 netmask for this VE. The special problem we have is that (as in fact we're using a /16) the IP 10.116.5.255 can't talk to this VE anymore as this VE thinks this is its broadcast.
Please fix this asap - this breaks a whole network and I would never even have thought that someone would assume this crazy stuff as any VE is always /32 for its IPv4 address - especially as it is a link and no kind of broadcast-medium...
thank you
hk
PS.
pveversion -v
pve-manager: 1.9-24 (pve-manager/1.9/6542)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-47
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.32-6-pve: 2.6.32-47
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-2pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.0-6
PPS. I assume some changes from upstream vzctl-3.0.29.2 haven't made it completely into this vzctl.
well, I rebooted some hardware-nodes to get the latest 2.6.32-6-pve kernel to work.
The problem that arises is now that ipv6 shows up in the VE though it is a system based on debian-3.1 template (which should normally prevent the script to inject v6 configurations in /etc/network/interfaces).
And the much bigger problem is the assumption that seems to be made about the IP that is added to this VE:
auto venet0:0
iface venet0:0 inet static
address 10.116.5.1
netmask 255.255.255.0
broadcast 0.0.0.0
because we never configured a /24 netmask for this VE. The special problem we have is that (as in fact we're using a /16) the IP 10.116.5.255 can't talk to this VE anymore as this VE thinks this is its broadcast.
Please fix this asap - this breaks a whole network and I would never even have thought that someone would assume this crazy stuff as any VE is always /32 for its IPv4 address - especially as it is a link and no kind of broadcast-medium...
thank you
hk
PS.
pveversion -v
pve-manager: 1.9-24 (pve-manager/1.9/6542)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-47
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.32-6-pve: 2.6.32-47
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-2pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.0-6
PPS. I assume some changes from upstream vzctl-3.0.29.2 haven't made it completely into this vzctl.
