Hi, thanks for the info. We yesterday installed the amd64-Version on our new intel-boxes, everything ´s fine, 8GB RAm was recognized. Best wishes Fred

I get a full pfSense install into a 1GB SSD with plenty of space left over. I ran only a small number of packages. Some packages would require a much larger drive.

There have been lot of discussion of this already at this board

No, there is no alerting mechanism for that.

You may want to look at the nano installs (for 2.0), which allow limited package support. I'm not sure about the embedded kernel on the full install - searching the forum may provide you with more ;)

Yes, when you upgrade the firmware it reinstalls the packages. It may not be bandwidthd to blame, but the pfSense package install/uninstall for bandwidthd. I'm not sure who is maintaining that package, but you'd probably have more luck in the packages forum asking specifically about that issue there. It really has little to nothing to do with the firmware update other than that the update uninstalls/reinstalls the packages.

pfSense satisfies everything you need except the "daily bandwidth quota", AFAIK.  You didn't specify the speed, which would determine what kind of hardware specs you can get away with; however, if 10Mb or under (standard ethernet speed), an old pentium-class PC with 128MB of RAM will do fine. Keep in mind some things: 1. You said the ADSL modem has a wi-fi NIC on it.  You will obviously need to figure out how to disable it and keep it that way. (Network security) 2. What is to keep anyone from accessing the ADSL modem directly, bypassing your whole setup? (Physical security) 3. If you're using wireless from the firewall to the other computers, you'll not only need to do a site survey, but make sure whatever wireless NIC you select is supported by pfSense; if 2.0, then this can be seen easily by seeing what FreeBSD 8.1 supports, which pfSense 2.0 is based on. 4. You didn't mention content filtering.  Since this is your family, I could see you wanting this.  Bear in mind that it will drastically increase the hardware requirements if you do this or any other major proxying or deep packet inspection with Snort or the like. Good Luck! Mike

@Highroller: A couple new updates for 2.0 RC3 came out today. After installing the updates I now have an RDD error. Can someone take a look at the attached long and give me direction on how to fix this or what to do? Thanks "UPDATE" I rolled back a couple configs and found the Errors where caused by Snort.  I was able to roll back to the point before the install of snort and all but one Error went away.  The one Error I'm still getting is: (apinger: Error while feeding rrdtool: Broken pipe). Anyone have an idea? Thanks

Your CF manufacturer actually made a bit smaller card than 4GB or one reason is that manufacturers define 4GB differently. In this forum we're already discussed this same thing over and over again.

@AvadaKedava: Hey everyone new to pfsense here looking to use it because I want it for it's good QoS for VoIP in my office.  I have 1.3.9 installed and running I believe, whatever the stable one is.  Is it a good idea to go to 2.0 RC3 or should I wait for stable in production?  Not sure how good pfsense RC's are, like if it's buggy and just for testing or if people use it.  Thanks! I have been running Pfsense over 2 years now and i would say Go to 2.0 and at least RC3 build. The features difference really makes it worth the effort (not that there is any) to install. Many of the features in the 2.0 release are tailored to the internet "now" vs the 1.2.3 had features best for back then. Does not make sense to start your builds when all forums including support are focusing on the new build. Many of the problems of the old are fixed in the new. **I hope you made your decision by now this was an old post,This is for the new viewers.

Ok, thank you for the help!

@wallabybob: A limited number of packages is supported on the embedded version. One of the intended application areas for the embedded version is for "disk" with a limited number of write cycles (e.g. compact flash). Thanks wallaby. I'll look into a SSD. By the way, I understand SSDs do not work well with Squid. Would I get any benefit from Squid on a home network and not running any web servers?

Good solution! :-) There are new snapshots every day. Here you can find the changelog of the snapshots. https://github.com/bsdperimeter It is not neccessary to update every day but it makes sense to do so once a week or every two weeks. If you think you found a bug, first check for an update and then report to the forum if the bug is still persistent.

You'll find that a USB memory stick is a great way to install as no optical drive is required.  I posted my newbie wanderings here: http://forums.smallnetbuilder.com/showthread.php?t=5379 Cheers, Dennis.

I tried "update error" in the search box and it gives me this: Pages: [1] 2 3 4 5 … 38 Maybe you are searching in just a particular section of the forum. For the Installation and Upgrades section: Pages: [1] 2 3 For 2.0-RC Snapshot Feedback and Problems section: Pages: [1] 2 3 4 5 … 13 Did this solve your problem? @stephenw10: Have you read this? http://forum.pfsense.org/index.php/topic,38687.0.html Steve

np, keep an eye on that board for 2.0 related stuff.

I have the same problems, albeit a bit different, I get this message only for one interface, when I try to put it into the same gateway group and put it on the same level to have loadbalancing. Connections trying to use the new interface fail and the connections do not work proberly at all (most of them time out). I use VLAN's for my WAN connections. Each ADSL Router has it's own VLAN and Network (a 10.100.<vlan>.0/28 net) where vlans are counting up from 100. So there is no overlaping. Another symptom I have is with the failover pfsense box, which when started does not recognize it's Backup and everything is Master, I have to deactivate CARP and activate it again on the Backup-Router to have it become Backup. Then all gateways are offline except the one which is on the interface which gives me the problems described above with llinfo stuff, it stay's online and I get packet loss on both, the primary and the backup box … The servers are no-name computers with Intel PRO dual-port server network cards. Hope someone can figure out what's going on, i have this since the Beta through 2.0-RC3 (i386) built on August 3rd. best, Ray</vlan>

@Gradius: I see. Thanks. But if you like to help the developers to fix bugs it is neccessary that you are running an actual snapshot so that they can narrow down between which snapshot there exists a new bug.

@stephenw10: Create the file /boot/loader.conf.local and add the line there. See: http://doc.pfsense.org/index.php/Boot_Troubleshooting This doesn't work for everyone but it does in most cases. Steve Worked for me!  Got the box working.  Thanks. Ken