Well, I figured it out. I was using a usb ethernet device with the MCS7830 chipset, that I had to load the kernel module to get recognized.  From here: https://forum.pfsense.org/index.php?topic=50241.0 It did recognize it, I could configure it and everything, but it just didn't work.  I pulled an old pci ethernet card out of the junk box and now everything works just fine. thanks everyone

details can be found here: https://redmine.pfsense.org/issues/2770

@imanz: I just wanted to let you know that it is working correctly after the change. Thank you for the quick response. Not that install and basic configuration is complete I will move on to correctly setting up all the subnets; will probably be back with more questions :) An OT question. Since I just installed pfSense 2.2.Beta on a similar set up, same board, same amount of RAM but using an INTEL S3500 SSD 80GB. I am using a M350 case, 1 Noctua Fan (40x40x10) blowing from the upper case directly to CPU and RAM. Can you kindly report your operation temperatures, case used and fans (number, position and flow direction)? Thanks

Firewall Log DNS Lookup Dialog Box Missing in 2.1.5 https://forum.pfsense.org/index.php?topic=81145.0

Pentium 4 chips were all single core with Hyper Threading.  They changed the name to include a "D" when they made them dual core.  Truth told though, HT was a liability on those original chips.  In many workloads they actually performed better if you disabled it.

1 - you should be able to give LAN devices a static IP like 192.168.1.2 up to 199, set its gateway and DNS to 192.168.1.1 (pfSense LAN IP) and it will have internet. The default LAN to any rule will allow all LAN addresses out. 2 - you need to port forward on each modem - since pfSense itself is a firewall, I usually just take the "port forward all" option on front-end devices. Often they cal it "DMZ" when actually it is just an internal private IP address to forward all traffic to. This way you do that on all 4 front-end devices 1  time only (no need to go back opening extra ports in future0. From a security point oof view it is nno different to bridging the front-end device through to pfSense. In both case all incoming connects (friendly or otherwise) arrive at pfSense. Then use pfSense as you normally would to port forward into your server/s. You will then want public DNS name/s that point to your public IP/s and have them point to a suitable list of your public IPs if you want outside users to be round-robin connected to your various public links… 3 - the firewall is already enabled. By default clients on LAN can start outgoing connections to internet resources, and all incoming connection attempts are blocked. Put pass rules on wan1-4 to allow what you want.

You could argue that the actual problem here is an underlying requirement to re-write the gui. That's a topic for another day.  ::) Your problem is almost certainly that you're running a Linux based OS and you've installed some Miscrosoft fonts. They have have been included in your distro or been a added as a requirement of some other package you installed. The key is that with no MS fonts installed it displays fine. With all the MS fonts installed (including Tahoma) it displays fine. However if you have only the basic package(mscorefonts) it tries to use Verdana which doesn't fit. See: https://forum.pfsense.org/index.php?topic=81049.msg443393#msg443393 Either remove all MS fonts or install Tahoma. Steve

lol , you are right about the font size . I don`t know why i did not remind myself of that !!! the gold item still have the same error , but i am not worried about it because my firewall is installed in my personal system , and since this here is not a company or a corporation then there is no need for 24h/7 support . thanks for the tip ;)

You should start a new thread for this unless your setup is exactly the same as the OP. Steve

Nice. Ware your t-shirt with pride.  ;D Stevd

Trick for my machine (a while ago) was changing the SATA ports from AHCI to "Legacy" in the bios. So, more things to look at there than just "turning stuff 'off' "

I'm often out of touch… On the off hand chance that it works, I'd love to know how well it works. Morbid curiosity.

Both NICs are on the motherboard.  I don't believe I physically unplugged the server so you may be on to something there.

Does 192.168.100.0/24 somehow conflict with your WAN? If not, then you have to change your client IP at the same time.  When you change your LAN IP, DON'T HIT APPLY.  Go to Services->DHCP Server.  It will need to be configured to offer addresses in the new IP scheme.  After that, you can go back to the interface and apply the interface changes.  You will then need to somehow make your devices release/renew DHCP.  You can either do this with something like ipconfig /release then ipconfig /renew, unplugging the ethernet for a few seconds and reinserting, or rebooting.

ok this should be in the virtualization section. sorry. Its working now when i reboot pfsense - i read about this in another thread. Is there any solution to booting pfsense "twice" ? This machine is running 24/7 so its not such a big problem and pfsense isn't rebooted very often.

Hello friend. I just got a industrial grade SSD card from RENICE. The performance is amazing. And they're now presenting some free CF, SD cards and SSD to Twitter followers http://goo.gl/o9we1A

The Updater checks the URL https://updates.pfsense.org/_updaters/version which is a file that contains the current version info.  Perhaps write a script that grabs it and compares it to your local version file in /etc/version.