Ok I got Squid to work. This thread may be considered closed.

That's one of the reasons I often take the "extra" (120-150 secs) time to do a manual install. It reinforces all those automatic details that happen behind the scenes - and come back to bite you  ;)

@Supermule: May I ask why?? The geek factor? It does sound like a fun project, though I wouldn't want to run it myself that way myself. I would want it installed locally so I don't have to worry about the NFS server going down and bringing down the whole network since the firewall/router would go down as well. In terms of actually getting it to work, try getting a regular FreeBSD machine booting via PXE first. I forget exactly how to do that, I'd have to check how I did it at work. Then just apply that to pfSense and it should work, unless the code that allows it has been removed. Once again, on a firewall, I don't think I would want to rely on another server working in order for it to work.

I'm with Steve on a possible hardware issue. As well as the memtest, I'd suggest a burnin routine.  The UBCD (Ultimate Boot CD, Google should easily find it) has some good all in one tools that are helpful in these scenarios. No point in using pfsense as your trusted firewall if you can't trust the hardware it runs on.

If you set it up with only a single interface it will appear as WAN but it will let you connect to the webgui via that. There won't be a DHCP server running on that interface so you'll have to set up a client with a static IP to connect to it. Once in the webgui you can add the wifi interfaces and swap the NIC assignments around. Keep in mind though that as soon as you add a further interface the default firewall rule that allowed you to connect to the WAN will move to the LAN so before you do that add a firewall rule yourself on the WAN if you'll still need to connect via it. What wireless NICs are you using? Many 'N' NICs are unsupported. Steve

FWIW, I ran into this same issue on a couple firewalls that were upgraded from 2.0.3 to 2.1.3. But not all of them for some weird reason. Seems to affect most traffic/packets graphs on the affected systems. Will try deleting the .rrd files I guess. There isn't a way to manually upgrade the affected .rrd files?

The vulerability was only introduced with 2.1 so you should not be vulnerable to heartbleed. Additionally OpenVPN is not vulnerable in its default configuarion: https://forum.pfsense.org/index.php?topic=74796.msg409174#msg409174 However that doesn't mean that your outdated install isn't vulnerable to all the other fixes that have gone in since 2.0.2.  ;) Steve

How do you have virtualbox configured for networking  I would assume the hosts interfaces are bridged to both interfaces and has no IP on its os for the WAN, and an interface on the LAN bridged to LAN of pfsense of pfsense with an IP on the lan interface of pfsense. If this is the case you should have no problems connecting to web gui of pfsense from your host machine.

@jimp: I've thought about that before several times. It would be useful, but it would be a lot of extra work and though it might help in some cases, it would make other parts more difficult/less intuitive. (e.g. when does a protocol choice on a rule get trumped by a protocol choice in an alias?) That's exactly what I meant. The priorization of that would be tricky to say the least. As PF rules don't mingle protos and port together, that would mean extra work to unravel the aliases into actual rules and what is the order of them. If PF's syntax were more along the lines of " <action>on <interface>src <ip alias="" table="">port <port group="" alias="">to <ip alias="" table="">port <port group="" alias="">[flags <flag flagmask="">]" and [port] was defined not as numerical but as combination like udp/137 or tcp/443, that would be easier to achieve in the GUI or with aliases alltogether. But as the "proto" section declares the protocol for the rule, it's quite a bit more complicated.</flag></port></ip></port></ip></interface></action>

For the  gateway monitoring I have setup 750ms/950ms and it seems to be stable since a few hours. And I have setup back the hardware stuff, because of the rules "one mod only at a time  :)". More to come later …

Thank you very much!

No its an old BIOS update, I read the link you give on me, the last option to fix BIOS Disk is to update the BIOS, but luckily I install my pfsense and maybe if I get pfsense work it out, that's the time I will update bios and try to setup pfsense in the SCSI raid setup.

Thank you :)

I don't think the disk was full, it was a fresh install and I believe it is a 150GB HD.  The only thing I set was the IPs for the LAN and WAN.  The file did transfer and the message reads "firmware upgrade in progress" and has been like that forever.  Do you think.  I'll force a reboot and see what happens.  Thanks again.

"the problem because i use google dns server, when i change to pfsense ip, i can conect to internet." That is not a problem, your lan rules allow you to talk outbound on 53 udp, so you clearly should of been able to use google dns.  Now possible your isp blocks access outbound on dns?  But what dns you use has little to do with actually connectivity. Either you had connectivity or you don't - some client not able to resolve www.something.com is not lack of internet access, etc.

It appears that this might be a hardware failure as I originally thought.  After loading Windows 7 x64 my network interfaces other than that dedicated IPMI one are not functional still.  Also failover on IPMI to the normal gigabit ports doesn't seem to work either.  Waiting to hear back from Supermicro support if I should send it back.

@anthonysawah: Hey everybody! I'm looking to setup pfsense on a virtual machine on my laptop… Can I do that with workstation? Yes, though you may not get great performance. Your laptop may not support any virtualisation pass-through features. @anthonysawah: I also already do have a home router thats connected to the modem. Can I still use pfsense without directly connecting to the modem? Yes, though you will be double NATing. It's better to have a public IP on the pfSense WAN interface if you can. Steve

Hi Pete and Steve, Thanks for your replies.  I will give DiffProbe a gander when I have a chance.  Thanks for the tip about that.  I've also mentioned it to my buddy who is much better educated on networking. We will let you know if it tells us anything. Unfortunately, I spent the better part of last weekend trying to get a StrongVPN client working.  So far, no luck.  Had to do a complete factory reset at one point, started over and tried all the various tutorials in the forum as well as links to other directions.  I'll post in the existing thread on that topic.  If you guys may be of help, I'd appreciate the input. @ Steve, I was able to get Amahi working.  I successfully turned off DHCP server on the pfSense box and gave that job to the Amahi box. Thanks again guys for sharing the wisdom! DW

No. It should only go back to the configure interfaces screen at the console if it can't find a valid config.xml file. That can happen if the config file is lost for some reason or if it contains a reference to a NIC that is no longer in the system. It also happens if you boot from the install media instead of the HD. Steve