PfSense + Untangle on ESXI w/1 WAN, 2 LANs

njkreger

Hi, I have a setup I'm working on with having pfSense and Untangle (bridge mode) on ESXI, with one WAN interface, two LAN interfaces (one for workstations, one for VoIP, with the VoIP net NOT being filtered by Untangle), and a management interface for ESXI. There are four physical NICs in the hardware (I really only needed three, two if I used vlans, but thought what the heck, I have four, I'll use them all).

Here's how I have it set up so far internally:

vSwitch0 - WAN - vmnic0
-pfSense WAN (static IP)

vSwitch1 - Crossover - no physical NICs (promiscuous mode enabled)
-pfSense LAN (10.1.0.1)
-Untangle WAN (10.1.0.2)

vSwitch2 - LAN - vmnic1 (promiscuous mode enabled)
-Untangle LAN

vSwitch3 - VOIP - vmnic2
-pfSense VoIP (10.1.50.1)

vSwitch4 - Management - vmnic3
-Just assigned an IP in the same subnet as the Untangle LAN

So here are the issues I'm running in to and could use help with:

1. The Untangle LAN works, DHCP is being served, I can connect to the internet, but only for a short period of time. Then everything just stops working. If I release/renew the NIC on my computer, it will be assigned an IP for about 1-2 seconds before it goes blank. Not sure what's happening here…

2. The second LAN interface for VoIP is dishing out IP addresses, but can't connect to the internet. Therefore the phones don't work (it's through a company that hosts the PBX, so all the phones need is an internet connection).

3. For whatever reason, on the Untangle LAN, I can ping pfSense (at 10.1.0.1), but I can't get to the web interface via IP. However, I can using the hostname and internal domain.

I do have a working version of pfSense that is currently running the network on a different server (virtualized along with Solaris) while I experiment with this one, so I know pfSense by itself works fine, and the WAN, LAN, DHCP, and DNS settings are the same between the two.

Thoughts?

njkreger

Nevermind. I did another install and it works fine now. The first install must have been messed up in some way, because I didn't really do anything different the second time around. I also didn't realize I had to add rules to the second LAN connection, and it works fine now too.