Part 1: Set up a dedicated server with multiple IP addresses. Build a remote lab with Proxmox and pfSense on an OVH dedicated server.
- Part 1 (Introduction, OVH configuration. You’re here!)
- Part 2 (Configuring Proxmox.)
- Part 3 (Installing pfSense.)
- Part 4 (Configuring pfSense.)
This guide details how to set up a remote lab with a pfSense gateway on an OVH dedicated server, including basic firewall rules for managing access to the router’s web interface, and use of Let’s Encrypt for SSL certificates.
First, we’ll configure the server and its IP addresses.
- Manage OVH’s failover IP addresses in one place, rather than having to manually set up the gateway on every single virtual machine.
- Protect traffic to your virtual machines with one user-friendly firewall.
- Use fewer IP addresses. Instead of having an address per machine, you can forward ports to machines which do not have a public IP address.
- An OVH or SoYouStart dedicated server. I am using a lower end SoYouStart server.
- A domain name (and access to its DNS manager). In this example, I will use the
- Images for pfSense and (in this example) Ubuntu.
Failover IP addresses
OVH allow up to 16 extra free (after the initial setup fee) “failover” IP addresses with their dedicated servers. These can be used to give a public IP address to a virtual machine. For the sake of this guide, I have two failover IP addresses: one for the router, and one for the first virtual machine, which I will make publicly accessible.
- From the OVH control panel, select “IP”.
- Select “Order IPs”.
- Fill out the order form:
- Server: (choose your server’s hostname)
- Number of IPs: 1 address
- Country: (your choice)
- Accept the terms and conditions
- Repeat the process a second time for another IP address.
You will shortly receive two e-mails with invoices. After paying, the orders can take a while to fulfill. Once you receive confirmation that your addresses have been set up, return to the IP management area to set up their virtual MAC addresses.
- Select “Manage IPs”.
- Select your server’s hostname in the “Service” dropdown.
- Click the “settings” icon (a cog) next to the first IP.
- Select “Add a virtual MAC”.
- Fill out the form:
- Name of VM: (this field is for display purposes only, so you can set the name to whatever you like)
- Type of virtual MAC: ovh
- You want to: Create a new virtual MAC address
Next, set up the second failover IP address.
- Click the “settings cog” next to the second address.
- Select “Add a virtual MAC”.
- Set the VM name (this is required but can be anything).
- Use the failover MAC address from the first failover IP.
Again, fulfillment of the virtual MAC addresses can take a few minutes. You won’t receive an e-mail when they are finished, so check back later to find out. After this, you should have a primary IP address with no virtual MAC address, and two failover IP addresses with the same virtual MAC address. The virtual MAC addresses should be the same because later on, we’re going to use a 1:1 NAT rule to route the second failover IP to a virtual machine. Any further failover IP addresses added to the environment should also be configured with the same virtual MAC address.
IP address reference
For the rest of the guide, I will use the following (made up) examples:
|Name||IP Address||MAC Address||Description|
|Primary||220.127.116.11||(none)||The IP address that was originally supplied with your server|
|Failover 1||18.104.22.168||02:01:01:e4:44:44||The IP address we'll use for pfSense's LAN interface|
|Failover 2||22.214.171.124||02:01:01:e4:44:44||The IP address we'll assign to the first virtual machine|
OVH gateway IP addresses
Gateway addresses for OVH IP addresses are the address, but with the last octet
254. This means that our primary IP address (ex.
126.96.36.199. This is documented in greater detail
Later, we will need (well, want) subdomains for memorable access to the services we’re configuring. Add some A records using your DNS manager (replacing my example names and addresses):
In the next part, we’ll install and configure Proxmox on the dedicated server.