Thank you for this

Ouch. Never the underestimate massive coincidental failure.  ;) Often things start to fail and go unnoticed, only when several things have failed or are failing do real problems show up. Then when you investigate you find what appears to be a string of failures but you look for a siongle point of failure because that seems more likely. Of course most of the time it is just a single point of failure.  ::) Steve

Thanks, I see this was closed a not a bug.  I have another pfSense system to install and I will see if I get this issue as well.

It is just for Nano installs. The are mounted RO by default and should have been since 1.2.3. 2.1.3 is built on FreeBSD 8.3 so you should be using those.  ;) Since 8.3 is still the current  it hasn't been archived yet so you can just add packages by their name directly without having to specify the entire path. Steve

You can set a proxy bypass in the client configuration/options on the individual workstations/browsers. Otherwise you'll need to make sure that your local DNS resolves the hostname to be the actual local/internal IP address of the web server.

Alright, thanks for the info. I will place an order for the APU then.

What I want to do is stop traffic between the 192.168.2.0 and 10.0.0.0 networks - Ive tried a few fire wall rules and also block private networks - from the interface section but I'm not having much luck If you block private networks on these interfaces there will be blocked everything, cause your LANs are private networks. Basically pfSense only allow traffic which is proper to a configured firewall rule. However on LAN interface there is a predefined rule that allow traffic from LAN net to anywhere. If you don't want this you have do delete or edit it to fit to your purposes. If you just want to isolate your 2 LANs add a rule to each interface to pass traffic, in the destination area check "not", select network in type-dropdown and in the underneath field enter the other LAN network and mask. Delete any other rules. This allow access to anywhere, but the other LAN.

same solution works for 2.1.3 :)

The problem has been solved! Set in a private ip in squid do not pass on it. Bypass proxy for Private Address Space (RFC 1918) destination Do not forward traffic to Private Address Space (RFC 1918) destination through the proxy server but directly through the firewall.

Same here. CPU Load 100% …

I just did a test with a single laptop and it seems to be working now. You are correct, the WAN does not need an address. I realize now that I have a separate issue when I consider what I eventually want to accomplish. I really want to block Internet Explorer from accessing the internet and I have just learned that a transparent squid will break the bridge. I will do another post for my new issue. Thanks for the help.

I've set up a draytek 130 vdsl same setup .. I found that this exact issue is due to the setup of the draytek. ensure you have setup the router correctly… and update the fermware to the latest verison a quick setup (ensure you save the config as asked and conferm settings at end as my draytek lost vlan tag each time) *** ADSL Connection Reset router factory defaults Compete Quick Internet Wizard Disable PPPoE/PPPoA client                    (internet access >> PPPoE/PPPoA) Enable PPPoe Passthrough                      (internet access >> PPPoE/PPPoA) *** VDSL connection Reset router factory defaults Enable vlan and enter tag                      (internet access >> general setup) Disable PPPoE/PPPoA client                    (internet access >> PPPoE/PPPoA) On MPoA set                                            (internet access >> MPoA / static or dynamic IP)                       a)  MPoa (rfc1483/2684) >>>  enabled                       b)  Encapulation >>> 1483 Bridged IP (IPoE)                       c)  MTU >>> 1492 If vlan is enabled in step 2 then no vlan settings are needed on the pfsense firewall hope this helps :) Bodie

Ha. Ooops.  ;)

OK so I up dated to 2.1.3 the most recent release and for the last 3 days my memory allocation has been sitting at 46 % Don't know what the dev guys did but she is looking nice and stable now! Thanks Steve

what kind of trouble are you having with haproxy? what config are you using? have you looked at the stats page of haproxy that backends are 'up'.