PfSense on VMWare, behind router: Cannot ping WAN if
I'm trying to setup a test instance of pfSense (1.2 RC4) inside VMWare Server 1.0.3 on XP. I gave the VM 4 NICs:
le0 -> LAN -> 192.168.1.1
le1 -> WAN -> 10.1.1.1
le2 -> OPT1WAN -> 10.1.1.2
le3 -> OPT2DMZ -> 192.168.100.1
The idea is a dual WAN setup with a LAN and a DMZ. The physical box (10.1.1.104) is in my physical LAN 10.1.1.0/24, a hardware router (10.1.1.120) dialup ADSL for internet access.
I have another XP VM with IP address 192.168.1.214, which I use to connect to pfSense's admin GUI without problem. I can ping 192.168.1.214 from pfSense's LAN if, I can also ping WAN if from OPT1WAN if. My router accept ping from 10.1.1.0/24, I can ping it from physical box (10.1.1.104).
The problem is I cannot ping my router (10.1.1.120) from pfSense's WAN if, nor can I ping pfSense's WAN if from the physical box (10.1.1.104). I have unchecked "Block private networks" in WAN setup, and added a rule to allow any to any on WAN if:
Proto Source Port Destination Port Gateway Schedule Description
* * * * * *
In firewall log (I turned on logging for the rule above), I can see the ping ICMP pass from the physical box to pfSense's WAN:
Jan 28 16:44:40 WAN 10.1.1.104 10.1.1.1 ICMP
and using packet capture I can see:
16:44:40.166767 IP 10.1.1.104 > 10.1.1.1: ICMP echo request, id 1536, seq 2816, length 40
But there is no reply, and naturally I cannot connect to internet from the 192.168.1.214 VM either.
Any idea how to debug this problem?
GruensFroeschli last edited by
Do you bridge the physical interface to the vmWare WAN?
If you meant I should set virtual NIC's setting to "Bridged: Connected directly to the physical network", then yes, I have done that for all 4 virtual NIC's. And in Manage Virtual Network, I have assigned my physical NIC to VMnet0.
PS: I only have one physical NIC, hopefully this is not a problem.