Excellent post grab3. I would love to see a tutorial for this. If you want I could host a tutorial on my website. This is something that really interest me and I am sure many people!

hansru, that only works for D series. I don't think ALIX C series support boot from a usb cdrom.

Hi Yes  I apologise just put last two sections of IP address I used these address4s before and pfsense seemed to work fine however I think that I must have bridged lan to Wan I have now kept same addresses and bridged and it appears to be working. Should I simply give wan card an "odd" address say 198.162.1.158 and unbridge What is the advantage/disadvantage of bridged Thank you again for your time

If you are trying to install pfSense to an embedded platform other than a …. How to setup NIC team on a HP ProLiant DL 380 for fault tolerance and Load

Ok I solved it.  Seems like my hard  disk had some remnants left over from an earlier OpenBSD install, and after that an IPCop install.  So this messed up the partition tables and hence the reason I got the warning about the broken GPT. I used dd if=/dev/zero of=/dev/ad4 and wrote zero blocks to the beginning couple of gigs and end couple of gigs of the disk.  This cleared the error and now pfsense installed just fine. HTH someone else.

Obtained a copy of 1.2 and it works fine. Please can someone fill me in on the bug reporting proceedure? Phil

Don't you guys think its funny that you all seem to have the same type of problem but no one has posted any help? Its because the problem has been covered a gazzillion times all ready. So I went back to the forum and searched again and some bloke said you need to disable UDMA in the BIOS, PIO only. I did this and bang both drives boot! http://forum.pfsense.org/index.php/topic,11016.0.html

The same with 1.2.3 from Apr 7 I guess I will just use kern.hz=100 and no polling.

See http://forum.pfsense.org/index.php/topic,14994.0.html and http://forum.pfsense.org/index.php/topic,15157.0.html

Can I suggest you actually perform those searches I suggested and look at that page.  The hardware that happily supports 100 users in one network may not be enough to support 10 users in a different network. Here's a bunch of things mentioned elsewhere that affect the answer: Type of NICs - server grade NICs have a lower performance impact than desktop NICs.  Some cards are known to be a bad choice. Traffic profile - of that 100 Mb/s how much do you actually use?  How much would you be pushing through pfSense?  What does that traffic look like, is it all long sessions, short sessions, UDP, TCP, little packets, big packets, what? What kind of Internet bandwidth do you have, 512 Kb/s, 50 Mb/s? What services are you running on the pfSense host? And so on, and so on, and so on.  As I said, this has been asked and answered many times before.  I'm not going to repeat the answers for everybody who can't be bothered to search.

Have you tried a base FreeBSD 7.1 install?

Hello, I have IPCOP and PFSENSE connected to the same router (82.102.x.x/29). Both subnet's use the same default GW (82.102.x.1) The subnet 192.168.16.0/24 work fine. The subnet 192.168.1.0/24 work's fine until it stop's, after a while it returns. I monitored the default gw IP (82.102.x.1) and it's stop's responding only in this subnet!

There are a lot of files in there. You want the latest one in the format of: http://snapshots.pfsense.org/FreeBSD7/HEAD/pfSense-2.0-ALPHA-ALPHA-yyyymmdd-time.iso.gz

Dont put an IP into the domain name field. Put here the name you own (corresponding with your public IP). If you dont have a name for your IP just leave it on the default.

FreeBSD doesn't yet support any "wireless N" devices hence pfSense doesn't.

@GruensFroeschli: If you switch NICs around you need to assign them afterwards under: Interfaces –> assign. when i start to install–-- add hardware network adapter chose manufacture==level one chose cd drive installed but it s till not working (it appeared with error code 10)....

The cause of all my troubles appears to have been the finicky BIOS of this box. The trick is to have one setting for when booting of CDROM and installing to HDD, and then change the settings back to Optimal Defaults after having installed. Oh, that as well as disabling DMA access to the HDD with appending of hw.ata.ata_dma="0" to the /boot/loader.conf. AND - you MUST unplug the CD drive (even if there's nothing in it and the BIOS is configured to boot from the HDD first!) It may sound like the bleedin' obvious to people reading this now, but it confused the hell out of me!