I was a Slashdotter until I found Hackers News. Within the first few days of browsing I saw people like Moxie Marlinspike saying intelligent things in the comments and I was hooked. Very often, the article's author or the person whom the article is written about will be in the comments. Sure… there are still comments that are pants-crapping insane, but that's life. :) Slashdot is dead.

@Harvy66: FreeBSD 11, summer next year, will have a slew of huge improvements for nearly everything related to VMs and network performance. Then it's a matter of waiting for PFSense to get rebased. You seemingly have no idea how trivial it is to 'rebase' now. What was true in the past is no longer true with the changes we've made to the build system for 2.3 and beyond. In other words: We fixed that shit. Point-in-fact, 2.3 follows -STABLE.  When it is released, we will be so far along the path to 10.3 that the eventual upgrade will be a non-event (and likely carried out entirely via "pkg update;pkg upgrade", or the GUI equivalent.) We have an internal project that follows -CURRENT (FreeBSD will be the eventual -RELEASE of what is now -CURRENT), so that will also be trivial. Mostly, it will come down to testing.

Ok, will do.  Is there any reason why they are using multiple sources for trace route? (Wouldn't it suffice for just one machine to send the packet rather than 50 or 100?)

Glad you were able to get yourself up and running. If you hunt around the forums you'll find a vast amount of accumulated knowledge and tips.  Some take more work than others to find, but well worth the effort IMHO. Welcome to pfSense  :)

@Phishfry: I was thinking more along the lines that you would not include a web server because there are so many different web servers, but that there is only one main dhcp server used by both Linux and BSD's. The ICS one with many versions in use. I do notice that debian ships without a dhcp server included as well. No big deal at all I was just wondering if there was a back story. This might have to do with the pupose of the server. dhcp is used mostly by internal networks - such as bootp, nfs, samba, etc.. maybe one reason, a good one by my account. Then these days, dhcp is nearly certain on internet routers by ISPs. So, two dhcp servers on the same network is trouble so is the fact that dhcp is tied into so many bootp, dns, and other servers/services So - dhcp is NOT internet friendly, NOT isolated to a few calls such as a database server, and really a joy-kill comes to improper config - NO NETWORK! Limited but essential, No, I have no idea why FreeDSB does not ship with dhcp Debian ships with NO UNECESSARY servers - like ??? Wow! Go Debian!

that would require that we move away from CARP. I don't discuss future plans here.  (try reddit… lol)

Le gonzopancho est mort, vive le gonzopancho !

Check out: https://forum.pfsense.org/index.php?topic=56941.0

figured it out.. set a static ip on the lan with the gateway the same as the LAN interface and connect wifi to existing network…

Wrong section but here's how you configure the AD authentication for pfSense. https://forum.pfsense.org/index.php?topic=44689.0 Pictorial guide:  http://www.geeklk.com/2014/03/pfsense-configuring-windows-active-directory-authentication/ You'll need to assign the correct groups and rights as you require.

I would suggest that your first troubleshooting step is to disable squid and squidguard, then clear out any tables those package have created. You can then verify that the desired traffic is passing through the firewall, which verifies your firewall rules allow it to pass. Once you have things working without squid and squidguard, you will need to reintroduce those packages and debug your settings. If you have a squid or squidguard problem that you cannot solve, I suggest you post again in the Cache/Proxy forum.

Won't affect the existing ones since they're already tagged, and by changing it in the portal it'll apply correctly going forward. Should be good.