Thanks for the feed back. Just realised that iocage needs zfs. I probably go with with ezjail instead.

I am far more familiar with ESX over HyperV, but I think you might find that ESX has some advantages over HyperV Lighter weight. More of your server's RAM and CPU cycles will be available for your virtuals. Easier networking. ESX's virtual switches are easier to configure to accommodate the scenario you describe.

I received a follow up reply from them. Thank you for getting back to us. We are happy to hear that has been self-resolved. We would like to let you know that we had specific issues with Dynamic DNS after the release of new account panel. However it seems to be working the time being. We are still fixing and organizing the things in order to avoid such issues in future. If you experience any issues after it works please contact us back and we will gladly assist you. In the meantime, should you have any queries, please do not hesitate to contact us. So there we have it. I'm glad it wasn't anything with pfSense at all. Thanks

SSD works and some shitty USB stick doesn't? Well, that's really shocking…  ::)

Oh thanks, I will try remove BandwithD and reinstall it later.

@sreekupm@gmail.com: I have Sonicwall T210, How to install Pfsense into T210? Not possible, those are MIPS rather than standard x86 like the Watchguard and similar boxes that people repurpose.

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.