1
24.1 Legacy Series / Re: No Internet Access - OPNsense on VMware
« on: August 17, 2024, 12:13:27 pm »Quote
10.29.251.10 is a device on the LAN of OPNsense (OPNsense is the DHCP server providing this IP address)I repeat... 10.29.251.10 isnt bound on an OPNsense interface you cannot simply spoof a LAN ip. Why dont you ping from 10.29.251.1 (your opnsense gw??) or use that host 10.29.251.10 to ping?
I could try to ping 8.8.8.8 with the source being the LAN bound address (In this case, it is 10.29.251.203)
• OPNsense CANNOT ping 8.8.8.8 with source set to 10.29.251.10"
I'm not familiar with ESXI but i use proxmox on many devices.
I just finished fresh VM installation of OPNsense, 24.7 didnt workout thus went back to 24.1.10 for now.
Your setup is simple, there's no reason it wouldnt work. You're missing something obvious..
By default any host on OPNsense's LAN that got its dhcp from OPNsense, will be able to access WAN/internet if its up.
Since your WAN gives a local IP range, disable block private networks.
With VMXnet3 you can build your VMs on top of that interface, which I assume its for lab testing if you want to do failover. You may have read, ideally should use vt-d and dedicate LAN/WAN NICs to the firewall for best the performance and least overhead.
Add 3rd NIC using VMXnet3 as your DMZ or VM network, just a bridge without anyvirtual port and doesnt bind to any physical port.
For lab testing failover etc, VMXnet3 as configured should work as well.. Is your RTR using VLAN to access its internet? I think you need to manually set NAT rules as the default on WAN wouldnt work. Instead do it on the wanVLAN.
Let OPNsense do the DHCP to avoid complications.
- On a fresh install there is a LAN to any rule
- Add NAT onto the correct WAN interface.