Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


ProxMox + NAT for KVM - Anyone got a good tutorial?
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

ProxMox + NAT for KVM - Anyone got a good tutorial?

I'm working on setting up VMs on a dedicated server I recently got, but due to my lack of IPS I am planning to use NAT for the VMs.. however, I haven't been able to find a good guide on how to do this.. can anyone provide one?

Comments

  • http://help.ovh.co.uk/Proxmox

    A few of items in that article are geared for OVH's network, but the follow the instructions under the section for "create a vm nat", they are generally applicable.

  • The way i did was installing ipfire in a KVM VM, and attaching 2 network interfaces(1 to outside, and one for VM's).

    Gave +8ms latency but it worked well with a nice webbased UI to configure.

  • @dabtech said:
    http://help.ovh.co.uk/Proxmox

    A few of items in that article are geared for OVH's network, but the follow the instructions under the section for "create a vm nat", they are generally applicable.

    That is useful, though I still don't fully understand what I'm doing :P

  • I've done this a number of times; just follow the guide here:

    http://www.ameir.net/blog/archives/55-running-proxmox-behind-a-single-ip-address.html

    Thanked by 1craigb
  • @amhoab funny, I stumbled across your guide a few weeks back when setting up my Delimiter dedi - it worked perfectly so thanks for taking the time to share that!

  • I've got this setup on a dedi, I am using VMWare ESXi but config is very similar.

    This is what you need to do:

    1 - Setup Virtual NIC

    2 - Create some VM's you want and bridge them to the virtual nic

    3 - Create a KVM VM with pfSense

    4 - Bridge the pfSense VM to your real NIC.

    5 - Make sure the pfSense VM is not set to start on Node reboot.

    6 - Start pfSense and continue with config. Set the WAN NIC as your Real one and the LAN as the virtual nic which the other VM's will be connected to.

    7 - Enable DHCP

    8 - Setup another KVM VM with Linux Puppy.

    9 - Console into Puppy and open a browser and browse to 192.168.1.1, use default pfSense details.

    10 - Change config and port forward pfSense port (80) so you can access remotely.

    11 - Add your public IP to pfSense as it's WAN IP.

    12 - If it worked you should have lost connection to your server. (IP Conflict)

    13 - Reboot your node and you should regain access.

    14 - Set the pfSense VM to start on node start

    15 - Set your node to DHCP and reboot.

    16 - Now browse to your nodes IP and you should see pfSense.

    17 - Port forward Proxmox and it should work.

    18 - Setup VM's and port forward what ever you want.

  • @amhoab said:
    I've done this a number of times; just follow the guide here:

    http://www.ameir.net/blog/archives/55-running-proxmox-behind-a-single-ip-address.html

    That looks like it would do it, but I'm insanely new to this, so what would I have to put in the installation in the VM for this to work?

  • @Void_Whisperer I will post my config file tomorrow! I know how to do it.

Sign In or Register to comment.