Search results

That table per se looks good. Can you ping the proxmox machine from the gateway? Also: 192.168.1.0 does look awfully like a network identifier. Try with 192.168.1.1

You have more serious things to worry about than the network config. If you know Linux well: you can try to fix it, otherwise I'd suggest to start over with a new Proxmox install.

You mean vgextend fails?

Still running 2.3, but will upgrade.

I really don't know. But logic would say you should be able to send any packet. In the worst case you just need to permit that on the host.

Do you route the VM IPs? What about /etc/network/interfaces on proxmox node VMs: /etc/sysconfig/network, /etc/sysconfig/network-scripts/ifcfg-venet* or /etc/sysconfig/network-scripts/ifcfg-eth*

Not talking about cables, I mean the network config on the node and the VMs.

The venet0 and venet0:0 are virtual interfaces, under normal circumstances they don't need a HWaddr other than 00-00-00-00-etc. Venet0:0 should be the correct interface, not sure what ether-wake needs.

Details? (I'd guess that something is wrong with your config, but that info won't help you.)

Can you ping the VMs from the node? We need more info, network setup for instance.

Hi, just wanted to point your attention to a recent explpoit that can kill the entire node from within an OpenVZ container (works on Proxmox - tested!). Details at: http://www.webhostingtalk.com/showthread.php?t=1280486 Red Hat: https://bugzilla.redhat.com/show_bug.cgi?id=979936 (not posting...