I have a set of VMs running under XenServer on OVH dedicated servers.
I'm currently using a Firewall which plugs into my vRack and acts as NAT to servers in the vRack and is also the default gateway. It sits in front of servers in a local address range 172.16.x.x
However I also have a public RIPE block which has it's own gateway IP.
What I would like to do is not use the firewall any more (as it's old) and use the RIPE block for incoming traffic which then gets sent by my load balancer via another network interface to the private address range - this all works.
However the problem comes in configuring the VMs on the private address range so that they can communicate out (presumably via the gateway IP on the RIPE block), at the moment they use the internal address of the firewall as the gateway but that won't work as I want to switch it off.
e.g. I have a VM running on 172.16.1.1 currently it's gateway is 172.17.0.254 - which is the local address of the firewall, which I want to remove - but since the VM doesn't have an address in the RIPE range it can't use the RIPE gateway?
tl;dr what should I use as the gateway on a vrack?
vRack servers communicating out via
Related questions
- Blacklisted IP ranges by UCEPROTECTL3
38834
23.02.2021 09:08
- Hot to delete my account?
37120
29.07.2018 19:49
- Proxmox + opnsense
31050
19.07.2018 15:53
- Free easy to setup OpenWRT NAT firewall for OVH (c)ESXi dedicated hosts
30825
16.05.2022 07:18
- Upcoming change: EFI System Partition over RAID1 for Linux installations
30766
08.10.2025 16:29
- Network Resilience Improvement for LACP aggregation on OVHcloud Bare Metal Servers
29236
27.10.2025 11:21
- .iso install on IPMI very slow
28302
22.05.2018 11:14
- Purchased a dedicated server - Awaiting Validation on a Saturday
28292
19.05.2018 20:07
- KVM error, blank screen, not send Keys
27997
11.12.2021 11:45
- Can't cancel/return server
26259
25.06.2018 08:31