It's all being kept carefully under wraps. The only clue we ever has was this tweet in which Scott says:

@Scott:

Later this summer we will change how large scale deployments of pfSense are managed

Clearly that time period has passed so you'd have to ask Scott.  :-\

Steve

Just checked in a fix in the tree for upcoming 2.0.1

@st4rtx:

hello all

i cant find any good pakage for pfsense to use snort sam
any body now how to use snortsam in pfsense ?

Developers are working on that:
http://forum.pfsense.org/index.php/topic,27388.0.html

Check here as well:
http://forum.pfsense.org/index.php/topic,34751.0.html

Consider them stable when you can build them into a wall… like a Novell ;)

Sounds to me like it's not so nice and stable as you say…
Perhaps this behaviour is fixed in the current release?. Maybe you should test that in a lab?

Glad to "contribute" in some way with pfSense  :D

Ahh, well thank you gentleman. I have learned even more!

@stephenw10:

You need to modify your firewall rules to prevent outbound port 80 connections. By default all traffic on LAN is passed.

Steve

WoW !!! Yes Steve, I got it, many thanks, I'm really greatful, you saved me from a lot of troubles ;)

I'm fairly sure that by default you entire disk is partitioned and mounted and most of that will be available to the squid cache. However it's been a long time since I used a full HD install.
To check you can run the command:

df -h

Either in the console or in Diagnostic:Command Prompt in the GUI. You should see something like:

$ df -h Filesystem          Size    Used  Avail Capacity  Mounted on /dev/ufs/pfsense1    443M    139M    268M    34%    / devfs                1.0K    1.0K      0B  100%    /dev /dev/md0              38M    2.9M    33M    8%    /tmp /dev/md1              58M    12M    41M    23%    /var /dev/ufs/cf          49M    1.6M    44M    3%    /cf devfs                1.0K    1.0K      0B  100%    /var/dhcpd/dev

The above is a NanoBSD install so your output will look different. Squid stores it's cache in /var so that's what you want to be big.  :)

Steve

Yeah, that kicked it back into gear.  ;D

Now my log is flooded with:

dhclient[5428]: DHCPREQUEST on re0 to 10.252.48.1 port 67 dhclient[5428]: SENDING DIRECT

Messages every minute or so again.  :o

Cheers.

There are no build tools included in pfSense as this would only serve to reduce security.
If you need to compile new drivers (it may not be possible) you need to do it on a FreeBSD 8.1 install and then transfer the file.

Steve

Just want to say something to the Squid Proxy point:

It would be able to install a squid proxy on each tower and another one at the main office. Then you have to enter the proxy at the main office as the upstream proxy for the tower proxies.

But I think this would only make sense if the bandwidth between the towers and the main office are to small.

Get all the easy stuff out of the way first:

Test your memory with memtest

Test your hard-drive with the manufacturer's utility

Install pfSense 2.0 Release, it's been out for a while now (do your config from scratch for best results and do not install ANY packages)

Make sure your hardware (especially your nic cards) are on the freebsd compatibility list

You either will need to swap out your production machine for this, or do the work after hours. Once you have done everything above, come back and let us know how it goes.

Yeah I'm more or less wanting something that is done via the web interface or the ssh shell to do it for me.  Then keep that config going forward with out having to redo it every firmware upgrade.

PFSense can do this for you.  Look at the wiki for VPN instructions.

http://doc.pfsense.org/index.php/VPN_Capability_IPsec
http://doc.pfsense.org/index.php/VPN_Capability_Overview

@clarknova:

Check the firewall rules on the interface that the laptop is connected to. If you have a Pass All rule then nothing will stop it from reaching hosts on other networks.

If you want to prevent that then try creating a LOCAL alias for all your local networks and modify your Pall All rule to include the destination !LOCAL.

Makes perfect sense.  I'll get that setup and retry.  Thanks!

squid + squidguard.  Read the packages forum.  This question gets asked a lot.