Look in the system log for any miniupnpd-related entries. In the console, do "ps auxww | grep miniupnpd". If no miniupnpd process is found, do "/usr/local/sbin/miniupnpd -f /var/etc/miniupnpd.conf -P /var/run/miniupnpd.pid -d" and see what it says.

Just be careful when you "extend" your subnet. If you forward broadcasts across the, then devices from one datacenter may pick-up an IP and use the gateway from the other datacenter.

You'll probably not want to allow broadcasts, which can cause issues with some services, or limit each datacenter on which devices get an IP address from the relative local DHCP.

I do not have experience in this area, so maybe someone else could add more to this, but I know this could be a real issue.

I'm assuming this is a full install and not nano. Putting aside the issue of a possible memory leak, you generally make swap permanent by adding it to /etc/fstab. Something like:
#/dev/label/swap0              none            swap    sw              0      0

Ref. https://www.freebsd.org/doc/handbook/adding-swap-space.html

To increase the size of the swap you will need to repartition the disk or create a "swap file" (see link above) and add it to fstab as above.

But… I don't think that's the problem. You should not be running out of RAM (and IMHO not even swapping at all). Other than the ICAP errors, what are you seeing that leads you to suspect the memory? Are there memory related errors in Status: System logs: General?  (i.e. out of swap space, memory exhausted, unable to create, etc.) In your situation,  I'd recommend looking for the source of the ICAP errors first.

Probably is that old option in postfix that I mentioned in the other linked thread. It tries to change system.inc in a very dangerous way. The package maintainer will need to fix it, so you'll want to make a post in the Packages board to get their attention.

Hmm, odd. It worked fine before though?
Anything vge related in the system or boot logs?

Steve

@Nightfrost:

–UPDATE--

So, after some worsening packet loss, and longer downtime periods, I decided to contact Verizon.  They are blaming poor cable installations between the ONT and my router.  I've already re-terminated one end, but I'm not too convinced that the chord would causes such an issue.  If the chord was damaged, i'm pretty sure I'd be experiencing other issues.  Also, I decided to pick up an Intel NIC to replace the PoS Realtek one.

Have you tried temporarily replacing the pfsense router with the old verzion router and seeing of you still have latency problems?  Could be useful as a way to rule out ISP/ONT/cabling issues.

I'm faulty as you  :P

WOOOOOOOOOOOOOT finally got it!

So I must have had a typo the first go around. Here was the solution:

/etc/rc.conf_mount_rw    # Set file system temporarily to read write
setenv "TMPDIR" "/root"    # Set the environment variable so pkg_add uses a location with enough space
setenv "PKG_TMPDIR" "/root"    # Set the environment variable so pkg_add uses a location with enough space
pkg_add -r -v ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.3-release/Latest/openjdk7.tbz    # Fetch openjdk7
rehash    # Updates executables available in path
java -version    # Tests whether JAVA is working

Thank you all for your help

The gateway address seems to be a private IP, is it conflicting with the LAN subnet?

Steve

No that there is anything much to see/change, but the settings for the monitor types are on the Monitor tab in the Load Balancer settings.

It sends a ping once per second, I don't believe there is a way to tweak that.

It's expected. The older version is used by some base OS components, but it does contain patches to correct the vulnerabilities.

Yes I am.

I found the problem. I had an OpenVPN server configured for incoming traffic and ended up with equal cost routes for the same subnet via each tunnel!

You live and learn….

Thanks

Switch off your modem for a while then try again.

See here

This has been resolved. Squid cache was corrupting the downloads and it was coming from Windows Updates. Setup WSUS server to correct this, little annoying how it can't tell you what the source IP address is.  :(

You could, just as an example, put your NAS or media server on a separate VLAN and then bring that into the ESXi box. Then you can add that VLAN as a separate inerface in pfSense and filter traffic to/from it.
You can probably have WIFI traffic assigned to a VLAN in DD-WRT and filter/route that separately in pfSense.

Many combinations are possible.  ;)

Steve

^Exactly. No need for three routers unless you have some other physical restriction we don't know about.

Steve

@lbm_:

@G.D.:

Do you see the correct [EAP] authentication method advertised with the SSID, when you scan the WiFi band?

How can I check this? As I remember it, I cannot see these details from the WLAN clients?

Any kind of half-good WiFi scanner should be able to display that. I use the free WiFi Analyzer by Kevin Yuan, for example.

I am glad you got the issue solved.

@pbxman123:

How is pfSense with USB to serial adapter support, specifically with the FTDI chipset, can you or anyone comment?  Again the feedback is much appreciated.  Thanks.

They work OK for me whenever I need them, but that's not very often.  Check out the FreeBSD supported hardware list (http://www.freebsd.org/releases/10.0R/hardware.html) and the uftdi(4) driver in particular (http://www.freebsd.org/cgi/man.cgi?query=uftdi&sektion=4&manpath=FreeBSD+8.3-RELEASE)

It's good ? I will tire .

Awesome!  Thanks guys.

Rick