OVH Community, your new community space.

Public IP management.

13-03-2014, 22:16
It is described in the very last step of the OVH link given. You'll probably find more by searching "iptables port forwarding" or "iptables dnat"

12-03-2014, 09:35
Thanks Myatu,

Can you please throw some more light into... how to do the clever stuff with port forwarding.


11-03-2014, 07:47
Don't bother with OpenVPN - it is way too cumbersome and heavy for this purpose.

Search and ye shall find:

NAT is one option, which can forward a port from the public side (ie: to a VM in your internal network. Though you are restricted to only forwarding ports (but with some imagination, you can do plenty with that).

You can also assign a failover IP to a VM. If you're using a "veth" device, then you'll need to setup a "virtual MAC (vMAC)" with OVH first for that failover IP address before you assign it.

Otherwise, vRack with its own IP allocation would be the way to go.

You might also come across a few helpful, though dated things on my own site:

11-03-2014, 07:25

I have been playing with proxmox and stubbled on this guide which i found extremely useful.

I am just starting with one node at the moment, so i have just skipped past some of the clustering part.

I have succeeded in setting up a private subnet with openVPN and have created some VM with local IPs from the private subnet.

What i am struggling with is understanding how to safely bind or map public IPs to my local VMs ?


Is there a way to route independent (domain request like requests from my host proxmox instance proxmox IP) to the VM individually ?