OPNsense on OVH VMware with an IP Failover

[Baliste]

Hello,

I am migrating 2 client's physical servers on a OVH (French cloud actor) dedicated server with VMware.
I got the dedicated server, with an public IP adress and an IP Failover with a virtual MAC address.
The public IP adress will be allocated to the VMware server
The public IP Failover will be allocated to the OPNsense server.

I migrated my 2 windows servers on 2 VM, they are working.
I created a third VM and installed OPNsense (v.22.7), the goal is to use the OPNsense to protect the Windows servers and access them only trough OPNsense VPN. OPNsense is working but can't reach Internet.

On the LAN side, the Windows and OPNsense are communicating, but on the WAN side the OPNsense can't reach Internet so the Windows VM can't neither

I already managed several VMware servers and OPNsense firewalls, but this is the first time I have to use an IPFO

The network is :

The VMware server IP adresse is : 51.xxx.xxx.96
The VMware server GW IP adresse is : 51.xxx.xxx.254
The OPNsense public IP address is the IP Failover : 91.xxx.xxx.64
The OPNsense GW is the VMware server one : 51.xxx.xxx.254
The OPNsense LAN interface is : vmx0
The OPNsense WAN interface is : vmx1

As the GW IP adress and the IP Failver are NOT in the same address plan, I have to use a route trough an interface and not trough an IP address.

I allocated the virtual MAC address of the IP Failover to the WAN to the OPNsense WAN Ethernet card in VMware.

I understood I have to have on my OPNsense :
 - default gateway : 51.xxx.xxx.254
 - a route to this GW using the interface vmx1

by using :
 - route add host 51.xxx.xxx.254 -interface vmx1
 - route add default 51.xxx.xxx.254

If I ping the GW, I get "Host is down"
If I ping the Internet (1.1.1.1) I get "No route to host"

Anyone already use an IP Failover this way ?

Thanks (a lot) for your help !

Frédéric

[Baliste]

How stupid I am ...

Everyting is fine with miy IPFO and my network settings in OPNsense, I just wrongly assigned the Ethernet cards in VMware, I switched them and it's OK now ...