0

Here is my network:

Client -- WAN -- PfSense(VMWare) -- LAN -- vSwitch (Promiscuous)
                                           \-- ESXi Management (192.168.2.1)
                                           \-- VM PC1 (192.168.2.100)
                                           \-- RealSwitch -- Server_1 (192.168.2.201)

OpenVPN server is configured as followed:

  • IPv4 Tunnel Network : 192.168.10.0/24
  • IPv4 Local Network : 192.168.2.1/24
  • Client can connect to VPN with success

And when I ping various machine, I saw this behavior:

  • Client -> PING 192.168.2.1 OK
  • Client -> PING 192.168.2.100 OK
  • Client -> PING 192.168.2.2 KO
  • Client -> PING 192.168.2.201 KO

So I can ping the two virtual machine located on my vSwitch. But I am not able to ping the network management of ESXi and I can't also ping other machine connected to the vswitch through an other switch...

All those pings work when I'm connected directly to my local network.

Do you have an idea what could be this problem?

  • Could you please clarify your statement? "I can ping the two virtual machine located on my vSwitch. But I am not able to ping the network management of ESXi" In your explanation you list the ESXi management interface as 192.168.2.1, and state the client can ping that IP address OK. – Mike Marseglia Dec 29 '15 at 15:04
0

You need two network ports on VMware to use pfSense effectively as a virtual machine.

vmnic0 - connect this to a separate vSwitch (named 'WAN'). vmnic1 - connect this to your existing vSwitch (rename it 'LAN'). This is the vSwitch serving the VMware management network.

vSwitchA (named 'WAN') -- \pfSense (NIC vmnicX interface configured for WAN access)
-------------------------------------\WAN link (cable modem or whatever)

vSwitchB (named 'LAN') -- \pfSense (NIC vmnicY interface configured for LAN access)
------------------------------------\ESXi management interface (192.168.2.1)
------------------------------------\VM_PC1 (192.168.2.100)
------------------------------------\Server_1

| improve this answer | |
  • As a related note, As of pfSense 2.2.5, pfSense running on a VMXNET3 virtual network adapter may have massive throughput problems unless you disable hardware checksum offload. See this pfSense article – ndemarco Dec 29 '15 at 15:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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