Hello all,
I have a dedicated server, running ESXi 6, for a lab environment. I recently had some problems trying to provide outbound access for the VMs, as I can't use the host's own address for this purpose.
So… I've ordered 4 more IP addresses, through OVH, for RIPE.
I'm not sure exactly what I need to do when I get them (or how long that's likely to take).
I'm fairly happy on the ESXi side of things, but presumably I can't just go assigning routable IPv4 addresses to the host, and hope the switch just agrees that the host's MAC address is supposed to be ARPing those addresses.
Does anyone know what I'll need to do to configure these addresses on the OVH control panel side of things? I didn't get much when searching the community.
In the meantime, I guess I'll just try getting IPv6 working while I wait for RIPE and OVH.
Hi!
So when using ESXi, you need to obtain additional IPs for your server and on those IPs you need to create virtual MAC addresses. Once you have them, on ESXi you need to set the VM to have the given virtual MAC address shown on the OVH control panel.
You will then need to configure the interface in the VM to use the IP address.
These guide should help you: https://docs.ovh.com/gb/en/dedicated/network-bridging/
Thanks so much for this!
I have my small block of additional IPs now. I think I'm missing something in the guides.
It seems to say that I should assign the failover IP to the VM (using the virtual MAC) for that failover IP, with a mask of /32, and a default gateway of the ESXi server's gateway (the .254 address).
But… surely, on a /32, the VM can't actually reach the gateway, because it's on a different subnet, and would need another gateway in between, in order to reach it?
Eg: VM 'failover' IP is 192.168.10.12/32
ESXi IP is 172.16.99.101
ESXi gateway is 172.16.99.254
How can 192.168.10.12/32 ever reach 172.16.99.254?
I'm ditching vyos and trying pfsense. Maybe that'll be easier for me to understand and configure.
No such luck. The guide says to use a mask of 255.255.255.255, but I can't set a /32 in pfsense. I can try /31, but again, the .254 address is on another subnet and therefore not reachable from the pfSense machine. Grrr.
> How can 192.168.10.12/32 ever reach 172.16.99.254?
A private IP address
- is an IP address that's reserved for internal use behind a router or other Network Address Translation (NAT) device, apart from the public.
Private IP addresses are in contrast to public IP addresses, which are public and can not be used within a home or business network.
Sometimes a private IP address is also referred to as a local IP address.
The Internet Assigned Numbers Authority (IANA) reserves the following IP address blocks for use as private IP addresses:
10.0.0.0 to 10.255.255.255
172.16.0.0 to 172.31.255.255
192.168.0.0 to 192.168.255.255
The hardware within a specific network that are using a private IP address can communicate with all the other hardware within the confines of that network, but will require a router to communicate with devices outside the network, after which the public IP address will be used for the communication.
This means all the devices (laptops, desktops, phones, tablets, etc.) that are contained within private networks around the world can use a private IP address with virtually no limitation, which can't be said for public IP addresses.
Private IP addresses also provide a way for devices that don't need contact with the internet, like file servers, printers, etc., to still communicate with the other devices on a network without being directly exposed to the public.