Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm running VMWare ESXi Free on a rented box.

I have 2 physical NICs, 1 connected to the Internet, one connected to the Private Network in our DC.

Each NIC is connected to a vSwitch and each vSwitch has a Management network and VM network (LAN/WAN).

Here is the diagram:

I setup the pfSense VM using the guide for vmWare in the docs.

During the pfSense Setup I set my WAN interface to one of my free Public IPs and did the same with a Private IP for the LAN interface. The upstream Gateway address is provided by the DC and was typed verbatim.

The DC opened up an SSL VPN for me to connect to the private network. Once connected to the VPN, I can access the ESXi host using its Private IP (, but I always get "Connection Reset" when trying to connect to the pfSense VM via its Private IP ( When I connect to the VPN I'm shown as connecting to and I'm trying to access (/27), could this be part of the problem?

pfSense cannot PING out to Google as well currently, however pinging Google's IP works just fine. I can ping the ESXi Host and I can Ping pfSense from inside pfSense as well.

Looking in pfTop while trying to access the Web Panel over private IP, I can see the incoming TCP connection, but as I said the Browser tries to connect for a little while then says connection reset.

At this point I have no idea what to do next and any help is appreciated.


I saw this: Virtual pfSense Appliance on VMWare Host and made the changes suggested by the answer (setting promiscuous mode to allow) and I can see the incoming traffic from my VPN IP to the pfSense private IP. But I cannot access the Web GUI still. (my pfTop:

share|improve this question
Why does each switch have a management network??? – Chopper3 Jan 18 '15 at 11:31
There is a disabled public management network in case of emergency that I can ask my DC to enable in the event of a catastrophic BOOM! – DavidScherer Jan 19 '15 at 18:32
That makes no sense at all but fine, whatever. – Chopper3 Jan 19 '15 at 21:11
@Chopper3 If the routing appliance (UTM) were to take a crap one day, my VPN also takes a crap preventing me from accessing the management network. In the event that this were to happen, I'd call the DC and have them enable the public management network so could get to the console and at least resolve the issue with the UTM and disable the public management network again. It's probably no the prettiest solution, but it's the only last resort fail-safe I could think to put in place that I could think of. – DavidScherer Jan 20 '15 at 22:01

(Not enough rep to make this a comment) This sounds to me like an issue with the default gateway or DNS servers. Please check this configuration.

share|improve this answer
There is no place to set the Default Gateway inside pfSense. Where would I configure these settings? – DavidScherer Jun 20 '14 at 16:33
Well, no place to set the default gateway for the LAN. I used the settings provided by the DC when configuring the WAN interface/ip. – DavidScherer Jun 20 '14 at 16:41

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.