I forgot to say I did try to open up the WAN interfaces a bit, but maybe not correctly. I setup this Port Forward rule:
NAT Rule --------- WAN TCP 8088 192.168.30.200 (ext.: any) 80 (HTTP) ... and a WAN rule to let everything in: Firewall Rule > WAN Tab ----------------------- Pass TCP * * WAN address * * I ping the pfSense VM using the web tool "Diagnostics: Ping" it can ping itself from the WAN Interface: PING 8.*.*.243 (8.*.*.243) from 8.*.*.243: 56 data bytes 64 bytes from 8.*.*.243: icmp_seq=0 ttl=64 time=0.713 ms 64 bytes from 8.*.*.243: icmp_seq=1 ttl=64 time=0.218 ms 64 bytes from 8.*.*.243: icmp_seq=2 ttl=64 time=0.225 ms --- 8.*.*.243 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss I'm still unable to access the WAN interface from any external machine. --- Ted > -----Original Message----- > From: Chris Buechler [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 12, 2007 12:21 AM > To: [email protected] > Subject: Re: [pfSense Support] VMWare ESX : Unable to access WAN > interfaceof pfSense > > On Mon, 2007-06-11 at 20:29 -0400, Ted Eiles wrote: > > Goal: Connect ESX/Dell to WAN port and use a pfSense VM as the > > firewall/vpn/etc. > > Issue: Unable to access WAN Interface of pfSense vm (ping, http, https) > > > > By default nothing will pass the WAN. You need to put in firewall rules > on the WAN permitting the traffic. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
