Problems with VM on different ip block/gateway then proxmox main ip

  • Thread starter Thread starter rvtech
  • Start date Start date
R

rvtech

Guest
Assume the following ip config:

ETH0/Proxmox IP: 1.1.1.1 (gateway 1.1.1.254)
VM1 IP: 1.1.1.2 (gateway 1.1.1.254)
VM2 IP: 1.1.2.1 (gateway 1.1.2.254)

Now, the problem is that VM2 is not reachable from outside.

It was working perfectly fine, untill I moved the harddrives out of the server, and placed them in a new server (old server's psu died, no spare...). On the new node, I had to comment two lines in /etc/udev/ruled.d/70-persistant-net.... to get Proxmox working.

I upgraded proxmox to 1.4 (was running 1.2), but not sure if that is causing this issue?:rolleyes:
 
Anyone who could jump in and help? Your advice is truely appreciated!
 
Openvz, running centos.

A few weeks ago, this vm was running on hypervm, but i then made a backup with the vz scripts to backup and restore it on this proxmox node. It was having issues like this aswell, cant remember how I fixed it..

If I check ifconfig, its showing venet.

Btw, i cant edit ips mem or space in proxmox on all vms coming trom hypervm.
 
Ok, ifconfig displays the following devices:

eth0
lo
venet0-00
vmbr0
vmtab101i0
vmtab102i0
vmtab103i0

The interfaces file looks as follow:

Code: 
# network interface settings
auto lo
iface lo inet loopback

iface eth0 inet manual

iface eth1 inet manual

auto vmbr0
iface vmbr0 inet static
        address  x.y.z.138
        netmask  255.255.255.0
        gateway  x.y.z.137
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

I have two VM's running on this proxmox server, one VM is working fine and running on x.y.z.140 (same block as proxmox) and one that is NOT working x.y.q.101. Both have the same /etc/sysconfig/network and /etc/sysconfig/ifcfg-venet0 file. The difference is in the venet0:0 file (which is showing the actual ip instead of 127.0.0.1).

If you need any info, please let me know! One of my VM's has been down since last weekend, and after many hours of debugging, I can't seem to find the fix.
 
After all this, I finally found the fix!!:D

I rechecked the bash_history AGAIN and this did the job!!

Code: 
sysctl net.ipv4.conf.all.proxy_arp=1

Ran this command, and within 5sec, everything is working!

The bug with errors when editing an openvz vm is still there though, but just let me know what files you need and I will put them online!
 
rvtech said:
Code: 
sysctl net.ipv4.conf.all.proxy_arp=1

Ran this command, and within 5sec, everything is working!
Click to expand...

maybe you should set that in /etc/sysctl.conf

rvtech said:
The bug with errors when editing an openvz vm is still there though, but just let me know what files you need and I will put them online!
Click to expand...

I need a container config file (/etc/vz/conf/<CTID>.conf)
 
You must log in or register to reply here.
Top Bottom