> -----Original Message-----
> From: Chris Buechler [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 12, 2007 1:17 PM
> To: [email protected]
> Subject: Re: [pfSense Support] VMWare ESX : Unable to access WAN
> interfaceof pfSense
> 
> Ted Eiles wrote:
> > 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.
> >
> 
> By "access", what are you trying? You won't be able to ping (other than
> from localhost) with just a rule allowing TCP. What you have is adequate
> to get into the webGUI (if the VM network the WAN is connected to is
> functioning and configured properly). I just installed an ESX VM last
> night, with appropriate allow rules on the WAN it works fine.
> 

Ahh, Ping > ICMP.  I double checked and yes I can get to the pfSense box web
tools and I found a mistake in a Port Forwarding NAT rule to access the
internal development machine's IIS webserver and now I can get to it also.

I did *not* use a static MAC address like the other fellow mentioned.

So, I can now say that pfSense can be used a firewall/VPN VM inside ESX to
protect VM's inside ESX that are on a different vSwitch.  This is great!!!

Thanks for the help --- Ted



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to