in the bios the CF slot is the secondary master , the first is for a sata hard disk ( but i dont have this )

yes the cf is fully inserted in the slot and yes it is the same CF ( new industrial CF ) as ipcop

so i dont see any solution

i check the setup and in the ide configuration nothing device but in the boot up sequence the first boot device indique 3M-conpact flash

so the boot is made normally on the compac flash

pj

No. pfSense is a complete system, not a package.

Yes, this is what i was looking for: there is a config.xml file i can export. Perfect, thank you.

BTW, how to "flush" the firewall by command line, just using pf command ?

You can backup your config and import it into 2.0. You should be able to upgrade from the GUI.
A common source of problems with this is non-standard characters in the config.xml file, probably worth reading through it to check first.

The ISO you linked to is the official RC3 release however it's a a bit old now. Newer snapshots are here:
http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_RELENG_2_0/livecd_installer/?C=M;O=D

Steve

I was about to say what wallabybob is saying…

I ran into some issues with my Atom boxes in terms of which RAID mode to choose, how to handle failures, etc... and in my experimentation, I am pretty sure I ran into the same error as you... mostly, in the case of when I had to drives RAIDed usign the built in RAID functionality (either Intel or ADaptec, in my case just the RAID feature built into the BIOS, not a hardware raid), then switched that functionality off to plain old IDE functionality (I'm using SATA drives). It appeared that pfSense just locked up mid boot... looks like it was looking for RAID controller drivers to initialize. It would just sit there mid boot.

This is why, I posted a question regarding this matter and what i was doing wrong... the overall response was to use the built-in OS based RAID features... since I could drop the drive into another box and it should still boot... This is what I am doing now for production environments.

It was also enough of a convincing issues to do the same thing on my Asterisk box.

Hope this helps.

Yes more ram is the reason most people switch to 64bit but I think 4GB is the limit on an Atom board anyway.
Here are some benchmarks: http://www.tuxradar.com/content/ubuntu-904-32-bit-vs-64-bit-benchmarks
It's Linux but I imagine the results would be similar for FreeBSD. They make the interesting point that a lot of 32bit code is compiled for i386 where as anything compiled for 64bit is at least i686 or newer so can use all the newer instructions.

Steve

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?