Help with additionals IP's from different Class

starnetwork

Renowned Member
Dec 8, 2009
422
8
83
Hi,
I post this Thread
http://forum.proxmox.com/threads/3322-Configure-Proxmox-with-different-IP-Class-s
and check this one
http://forum.proxmox.com/threads/492-Adding-VPS-on-other-iprange

finally, now I have clean proxmox installation - v1.6
Server connected with 1NIC - eth0
2 IP pools - for the same NIC (assign to the same vlan)
Pool 1 (useful): 92.88.135.64-92.88.135.74
GW: 92.88.135.61
Pool 2 (useful): 213.175.143.4-213.175.143.14
GW: 213.175.143.1

Proxmox v1.6 with vmbr0
I have 3 VPS based on openvz with centos 5.5 x64
VPS station 1:
5 IP's from the first Pool
92.88.135.65 - 92.88.135.69
2 IP's from the second pool
213.175.143.10,213.175.143.11

VPS station 2:
5 IP's from the first Pool
92.88.135.70 - 92.88.135.74
2 IP's from the second pool
213.175.143.12,213.175.143.13

VPS station 3:
1 IP from the second Pool
213.175.143.4

the problem is that on servers 1 and 2 the IP's from second pool (213.175.143.10-13)
not work
server 3: not work at all from the internet and to the internet

IP's for stations configured by: Virtual Machine Configuration -> Network Addresses (venet) ->IP Address

Host server (92.88.135.64):
/etc/network/interfaces
# network interface settings
auto lo
iface lo inet loopback

iface eth0 inet manual

iface eth1 inet manual

auto vmbr0
iface vmbr0 inet static
address 92.88.135.64
netmask 255.255.255.240
gateway 92.88.135.61
bridge_ports eth0
bridge_stp off
bridge_fd 0

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
213.175.143.11 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
213.175.143.10 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
92.88.135.65 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
92.88.135.66 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
92.88.135.67 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
213.175.143.13 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
213.175.143.12 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
92.88.135.72 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
92.88.135.73 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
92.88.135.74 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
92.88.135.68 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
92.88.135.69 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
92.88.135.70 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
92.88.135.71 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
213.175.143.4 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
92.88.135.60 0.0.0.0 255.255.255.240 U 0 0 0 vmbr0
0.0.0.0 92.88.135.61 0.0.0.0 UG 0 0 0 vmbr0

Please let me know what I need to do about this problems - on host, or on VPS stations
(additional IP's from second pool on servers 1+2 and IP from second pool for server3)
Please let

Best Regards,
Star Network.
 
Last edited:
Have you changed the line in your /etc/vz/vz.conf file:

NEIGHBOUR_DEVS=detect

should be:

NEIGHBOUR_DEVS=all

Make the change & reboot, let me know what happens...
 
work like a charm - Thanks! :)
can you please let me know What exactly does setting do ?

Best Regards,
Star Network
 
work like a charm - Thanks! :)
can you please let me know What exactly does setting do ?

Best Regards,
Star Network

From the vz.conf man page:


NEIGHBOUR_DEVS[="detect"]
Controls on which interfaces to add/remove ARP records for a container IP, also which interfaces to use to query/announce ARP.
If this is set to detect, the right network interface (the one which is in the same subnet as a CT IP) will be chosen automati-
cally. Any other value restores old (as of vzctl 3.0.19 or older) behavior, when all the possible interfaces were used.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!