1
General Discussion / ESXI WAN DHCP client is not working
« on: March 04, 2024, 03:59:14 pm »
I use OPNsense for many years running directly on hardware.
Now I've tried to run the OPNsense under ESXI on the same hardware, but facing to problems that WAN interface is not working (OPNsense do not get IP address via DHCP on WAN interface).
When I have running OPNsense on the same HW directly (without ESXI), then the WAN interface works fine.
Used configuration:
- ESXI 7.0 Update 3 and tried to use fresh installation of OPNsense 23.7 and 24.1
- Two Ethernet interfaces VMNIC0 (i219-LM) and VMNIC1 (i210)
- defined two vSwitches - first for LAN attached to VMNIC0, second for WAN attached to VMNIC1
- the vSwitch for WAN has enabled promiscuous mode
- OPNsense LAN assigned to VMX0 (LAN vSwitch), WAN assigned to VMX1 (WAN vSwitch)
The LAN interface works well (able to connect to ESXI, OPNsense web interface, console, etc)
The WAN interface didn't get IP address (see attached screenshots).
Note: When running the fresh installation of OPNsense on the same HW all works fine.
I've tried to search for similar issue, but found only hints regarding promiscuous mode, but this didn't help.
Thank you in advance for any hint.
Martin
Now I've tried to run the OPNsense under ESXI on the same hardware, but facing to problems that WAN interface is not working (OPNsense do not get IP address via DHCP on WAN interface).
When I have running OPNsense on the same HW directly (without ESXI), then the WAN interface works fine.
Used configuration:
- ESXI 7.0 Update 3 and tried to use fresh installation of OPNsense 23.7 and 24.1
- Two Ethernet interfaces VMNIC0 (i219-LM) and VMNIC1 (i210)
- defined two vSwitches - first for LAN attached to VMNIC0, second for WAN attached to VMNIC1
- the vSwitch for WAN has enabled promiscuous mode
- OPNsense LAN assigned to VMX0 (LAN vSwitch), WAN assigned to VMX1 (WAN vSwitch)
The LAN interface works well (able to connect to ESXI, OPNsense web interface, console, etc)
The WAN interface didn't get IP address (see attached screenshots).
Note: When running the fresh installation of OPNsense on the same HW all works fine.
I've tried to search for similar issue, but found only hints regarding promiscuous mode, but this didn't help.
Thank you in advance for any hint.
Martin