Proxmox VE 4 Network Problem with OpenVZ and KVM

[edvjellissen]

Hello, i'm new here.
First of all. Sorry, for my bad english. I try to do my best.
I am a Webhosting Company (myself alone). I have a root server by strato (germany ISP) and i have proxmox ve 4.0-36 on Debian 8 ( Jessie) 64bit installed.

I have many problems to connect my vms with the interfaces eth0 or vmbr0 or everything.
The IP of my Server is 85.214.254.185 and the gateway and boradcast is the same. The Netmask is 255.255.255.255.

I created a vm with the openvz container and i miss a setting "routed mode" venet. I can only use "bridget mode". But i think this is the wrong option.

I am very upset. Please, please, please can every one help me.


Thank a lot.

 

[wolfgang]

Hi,
in PVE 4.0 OpenVZ are replaced by LXC, so there are no OpenVZ.

If you want to use routed network, you have to set this up in the networkconfig

see
https://pve.proxmox.com/wiki/Network_Model

 

[Ovidiu]

@wolfgang

The other person didn't describe the situation all too well but I can relate as I'm trying to install proxmox on a strato root server too. They offer a second IP but their instructions are extremely outdated (debian 5/6) and they advise to setup eth0:1 and I'm also not sure how to get this working with proxmox routed setup. => https://faq.strato.de/article/1611/So-konfigurieren-Sie-Ihre-2.IP-Adresse-auf-Ihrem-Dedizierten-Server-unter-Debian.html#Bestellung%20der 2. IP-Adresse

In addition to that, their networking is quite confusing (for me at least) as I have never been able to switch my servers away from DHCP - no matter what I try, I can't get it to manually setup (even without the 2nd IP)

Any feedback from a Strato user would be much appreciated or maybe you can checkout their instructions and explain how that could work with proxmox?

 

[tom]

...
Any feedback from a Strato user would be much appreciated or maybe you can checkout their instructions and explain how that could work with proxmox?

Most hosting companies needs custom network configs - why don´t you just ask Strato if you are a customer there?

For a worry free Proxmox VE hosting, check our hosting partners.

 

[edvjellissen]

Strato can not help me. You are solely responsible for the hardware and not the software.
That tells me the support of strato. Because, i have a root server and not a managed server or an other product.

 

[Ovidiu]

@tom:

I need to urgently move a server and this strato server is temporary so I thought I'd make it virtual to make my life in a month or two easier when it will get moved to its final destination so I started looking at proxmox ve.

Strato's support isn'T very helpful at all, as you can see they even pointed me to the faq intended for debian 5/6 for setting up the 2nd IP.

But if there isn't any helpful pointer to be had here I guess I'll have to just forget about virtualizing it and try again in a month or two when it gets moved again to its final destination.

 

[Ovidiu]

@edvjellissen

after googling I found this thread: http://lug-owl.de/pipermail/linux/2008-March/029951.html

and apparently the problem with strato is one needs something like this but I am still not sure how to apply this config via the GUI:

auto eth0
iface eth0 inet static
address 85.214.82.17
netmask 255.255.255.255
post-up route add -host 85.214.64.1 dev eth0
post-up route add default gw 85.214.64.1

see the last two lines? apparently that is needed since the gateway is inside another network.

 

[localghost]

All people that have problems with Proxmox(4.x) on Strato Root Server plans.
Here is my working configuration:
1. /etc/network/interfaces on Host:

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp # this should always be DHCP

auto vmbr0 # internal bridge/network configuration;All containers VMs should be in this network
iface vmbr0 inet static
address 192.168.1.1 # internal network gateway IP address,e.g. this host internal IP address
netmask 255.255.255.0
bridge_ports none
bridge_stp off
bridge_fd 0

# this is for NAT
post-up iptables -t nat -A POSTROUTING -s '192.168.1.0/24' -o vmbr0 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -s '192.168.1.0/24' -o vmbr0 -j MASQUERADE

auto vmbr1 # another bridge for the second PUBLIC IP address
iface vmbr1 inet static
hwaddress ether 00:01:02:03:04:05 # duplicate the MAC address from eth0 adapter. Can get it with "ifconfig" command
address <pry.ip.add.res> # duplicate PRIMARY IP address that is given by the DHCP server to eth0 - see it with "ifconfig" command
netmask 255.255.255.255 # mask MUST BE 32 bit

bridge_hw 00:01:02:03:04:055 # duplicate again the MAC of eth0 - just in case
bridge_ports eth0 # !!! IMPORTANT !!! bridge ports of eth0
bridge_stp off
bridge_fd 0
bridge_maxwait 0

pre-up brctl addbr vmbr1 # initiate bridge
post-up route add -host <gw.ip.add.res> dev vmbr1 # add gateway for eth0 as known host - you can get it with "route" command
post-up route add default gw <gw.ip.add.res> # add it as gateway for the bridge too

up ip route add <sec.ip.add.res>/32 dev vmbr1 # route your secondary IP address


2. Container Setup:
2.1 one virtual ETH controller with static IP V4 your secondary IP address(the mask MUST BE /32). Use your primary IP address as Gateway.
2.2 one ETH controller in the internal network - 192.168.1.x for this example - where x != 1 as it is used by the host.