Ah. Here are a couple from Serve The Home: http://www.servethehome.com/tag/netgate/ There are also customer reviews on the pfSense and Netgate store product pages. We have a Netgate.com site in development, expect more in that space. edit: add line about customer reviews

Have look who provided this quality code Not Scott Adams?

Not looking too good for Free Beer with winners in California, Tennessee and Florida…

I started it here: https://forum.pfsense.org/index.php?topic=105184.0

Any thoughts on what the "two leading" encryption chips are?

@maverick_slo: Actually it will. I have it setup like this. Power has to be off at least 25 seconds so that green led on mobo dies. Then it will power on. If led dont die out it will not power on… Well that makes it easy, after I get the UPS setup and installed I will have to check this out.

@fantasypoo: I recently purchased a used 10/100 Cisco catalyst switch and figured it was time to upgrade to cat 6a from my old cat 5e cables. I decided to make my own cables and bought a spool of this superior essex 6A CMP cable. This upgrade made no difference at all and these cables aren't flexible at all!!! What were you expecting to happen?

I would: 1 - post this question in the "package / proxy" dedicated section  ;) 2 - go for standalone deployment. Reason for point 1 is that you will get much more feedback. Regarding point 2: this "package" approach is quite strange: although this is supported by pfSense and somewhat integrated in pfSense menu, packages are developed and maintained "outside". Risk of having misalignment in term of version is significantly higher and you will get better flexibility with your own deployment.

@Derelict: @Nullity: @Harvy66: Unfortunately, I have not done this ever/yet. Now that my wife and I are no longer having to eat ramen, we're going to discuss this topic. FreeBSD and OpenBSD. Two good investments. just finished a bowel of ramen & tuna (and hot sauce) myself. Not complaining though. :D A bowel of ramen huh. Sounds nasty. lol Shutup… :)

try updating

I remember seeing that (dropping 32bit) but I couldn't remember if it was for 2.3 or 3.0. At any rate I love pfsense, just trying to judge when I'm going to be forced to upgrade my old hardware even though I think it's kinda cool that 14 year old hardware can still have a purpose.

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  :)