Recent content by Winter79110

Udo; I'm sorry I did not see your reply before I posted my (hopefully final) solution for the problem we have been discussing. I wish I had known that! No harm done as I keep configuration records and notes manually anyway in documents used for debugging / training / reminding the team...

Mischief managed! After looking at Udo's last response and trying to comprehend the difference between the KVM and the OpenVZ networking approaches, I looked beyond the Proxmox world for similar problems (specifically, the error message "Connect: network is unreachable" under CentOS / Red Hat...

Udo; First, a brief progress report on the test I set out to do from the last post. H2 - Our local changes to the CentOS VM network setup have made it unable to reach the Internet Test A - Test by building a new Proxmox host and installing a fresh copy of the CentOS guest VM making NO...

Udo; Thanks once more for your expertise and ideas. 1) I tried your "tcpdump" suggestion and can verify successful round-trip traffic from the Proxmox VE host to the gateway and back (some interline spacing added for clarity): # tcpdump -i eth0 -n host 192.168.1.1 tcpdump: WARNING: eth0...

Thank you for your comment, Udo. I'm sorry for being unclear, but I will confirm that the VM I wrote about previously, from which I can ping throughout the LAN, is indeed a KVM-VM. Its (perhaps questionable) appearance under the thread "open VZ container has trouble reaching the internet"...

I would also like to chime in, with the slight variation that I'm experiencing the problem with CentOS in a KVM container. I just downloaded and installed Proxmox 1.7, then created a KVM VM and successfully installed a Centos distribution. The Proxmox VE inserted itself into the local area...