Confirmed the easiest way to handle this is with two drives- Used a 60GB SSD for the OS and the 3TB drive for just Squid, so far without any issues. Just used the shell after the install was completed, was able to easily configure the 3TB drive.

thanks cmb. since this is was a production system i just went ahead and restored back to 2.1.5 (did't have 2.2.4 install on USB drive) and restored the config. i'll check your suggestion when i'm going to be upgrading a couple systems (locally) soon. thanks for your help it was very helpful and yes I did have 192. dumb switch on the network (another thing I'm trying to slowly eliminate).

The quick/easy install is the best method to use for now, though last time I tried I was able to make custom partitions but it took some care. Might be able to drop to a shell prompt and make the partitions with gpart first and then just pick them during the install.

you can create it using vi or ee or upload it with your favorite scp/sftp client

If you register the hardware you should get access to the online HTML copy of the book which has a whole chapter on wireless and how to set it up and use it.

Here are the Intel cards. Single port only in PCI. Intel does have dual/quad but are PCI-X. I have never tested one in a regular PCI slot. I bought those Sun cards for next to nothing.. http://www.ebay.com/itm/381317244597

Is the default factory config still present in /conf.default/config.xml, or was that overwritten somehow by one of your own? If that file is still there, is it still OK? try "xmllint /conf.default/config.xml" – If that spits out the whole .xml file it's OK, but if it outputs an error then that's the problem. The behavior your are seeing would normally only happen if that file is missing or corrupt in some way.

@vsecgod: @Derelict: Note that you don't have to do every subnet on a firewall port.  You can do just the VLANs that you want to restrict, like the guest network. This would entail, in a nutshell: Remove the layer 3 vif on the VLAN in question from the switch. Tag the VLAN to pfSense Create the VLAN on pfSense Assign the VLAN to a pfSense interface Configure the layer 3 characteristics of the pfSense interface Configure the firewall rules to pass what you want passed If I'm understanding correctly, my current config is all vlan's routing on my sg300 switch.  You're saying remove the vif (virtual interface? forgive my noobness) from my sg300 and put it on the pf box.  So if I do this, basically other vlans still route thru my switch and traffic on the guest vlan route through the pf box? Yes.

@Gertjan: This was solved here https://forum.pfsense.org/index.php?topic=92709.0 from what I read over there. I saw: Under 512 megabytes of ram detected.  Not enabling APC. How much RAM do you have ? I have been able to stumble on through the install, and it's working at this point. 2GB of RAM in a Dell PowerEdge 850. After the installation of 2.2.4 I have gotten further with a functioning installation than any other attempt. Maybe I'm just learning a bit more  ???

How are you pinging the wan when out of the box everything inbound to wan is blocked - even ping.. Did you allow ping on the wan?  My guess if you say you can ping wan and not access lan is you have the interfaces reversed.

You cannot flash pfSense there.

@amfcandeias: Hi Gertjan, But i could install the file manager with no problem.. The DNS is configured, i can ping www.google.pt I install the 32bits because first i install 64 bits version and i have the same problem and i read that is a problem on 64 bits and squid… Do you think it's better the 64 bits? I'm usine sphere.. On the dns i configured 192.168.20.1 , 192.168.20.2 but on the main page appear that the dns servers are 127.0.0.1 , 192.168.20.2 and 192.168.20.1 . It's possible to remove the 127.0.0.1 ? Thanks I had exactly the same issue with 127.0.0.1 DNS address. I'm new to pfSense and this is my first test install of 2.2.4-RELEASE (Jul 25th 2015). First thing I noticed in Status: Dashboard - Version that new releases couldn't be checked. Also package installs failed to download problem. However, from SSH shell fetch was working ok. With Diagnostics: DNS Lookup I could see that files.pfsense.org would not resolve on 127.0.0.1, but only other DNS servers below. Apparently package installer does not use more than one DNS. So by disabling Services: DNS Resolver for now I could succeed with package installations. Hope this will help other newbies to get started.

Thanks, but I had seen all of those links already. I already did "dd" earlier, to completely clear the drive, so it wasn't a partitioning or GPT issue, or something left over from a previous installation. There's no SATA or AHCI options to set in the "BIOS" of the Soekris.  I think BSD is detecting the drives just fine, though, because they're all there, and the dd command completes without errors.  It honestly looks like some kind of scripting bug when it tries to do the partitioning. I found a workaround, though. Run the entire system from an external USB stick!  That's what I'm doing now.  The 4g-i386-nanobsd image works fine. Josh

Sorry ;-) Anyhow, I fixed it by using a x64 machine. In other words: Get the backup from the original, rename Interfaces in the XML File to different hardware and then restore it. Thanks for your help! Reinhard

That makes it fail the DNS rebinding and/or HTTP REFERER checks, where the hostname you're using isn't the hostname configured on the system. Either change it under System>General Setup, or add an alternate hostname under System>Advanced.

Supported != manual hack that can break any time.

Rather than re-configure the chassis -as in, installing the previous unit's hardware - the suggestion was to edit the config file directly so that LAN, WAN and DMZ (if any) assignments would be correctly mapped to the corresponding network cards on the new unit.