Ok, here's an update: pfSense is working fine on a different box (the one the store owner wanted to sell me in the first place!).  The errors went away on that box when the 2nd NIC was installed and it boots without error on that machine.  The firewall is configured and running smoothly now! :) The Netvista box wouldn't run with anything.  I'll play with that when I have time, but it's not a priority. And pfSense still doesn't boot on my Acer Aspire 5520-5912 AMD Turion X2 laptop, "oopsing" and spilling registers while still in the boot loader.  I'm taking a wild guess it doesn't like 64 bit chips or laptop hardware, but I really have no idea since it doesn't even hit the kernel yet when this happens. Thanks again to everyone for the help.  And as far as the thread on adding stuff, I'll make sure to read that later–maybe it is better, even on such a simple network as this, to run one machine as dedicated. Mike

Taken to german:  http://forum.pfsense.org/index.php/topic,7719.msg43500.html#msg43500

it's possible upgrade from 1.0.1 to 1.2rc4?

See: http://devwiki.pfsense.org/BootTroubleShooting http://devwiki.pfsense.org/BootOptions You should also try downloading the FreeBSD 6.2 (i386) ISO and see if that produces the same problem.  If it does then it's likely that your hardware (whatever it is - you still haven't said) doesn't work with pfSense/FreeBSD.

I have same problem but my problem was telindus anex B ADSL modem and when I change him with SpeedTuch modem everything work perfectly

eisa peittää

If you meant I should set virtual NIC's setting to "Bridged: Connected directly to the physical network", then yes, I have done that for all 4 virtual NIC's. And in Manage Virtual Network, I have assigned my physical NIC to VMnet0. PS: I only have one physical NIC, hopefully this is not a problem.

To make the DashBoard running after a PfSense update, you shuld do: Remove Dashboard Package Manual edit file /conf/config.xml, and remove from "<widgets>" to "</widgets>" Reboot Reinstall the Dashboard

You can leave them plugged. I suspect you dont have a DHCP on WAN –> per default pfSense tried to get an IP on WAN per DHCP. If it does not got one you have to wait until it times out. It WILL continue after hanging on this line. Just wait long enough.

Hi, just want to give a quick status about the situation: The 8408E (LSI Logic) isn't recognized in FreeBSD 6.2 / FreeBSD 6.3 by the mfi(4) kernel module / kernel. In the system is another SAS RAID Controller - LSI Logic AS1068 (integrated). I got this controller working with PFSense 1.2RC4 and the mpt(4) kernel module! I think this is the controller which Dell calls PERC5/i. Thanks for any interest - and thank you for this great project (best UTM interface out there!). Bye, unknown

Your /var is 17 GB.  Now repeat the du command inside /var.

blocked - myip:137, 138, 1035, & 1447 also occasionally myip:137 (source) - different ip (not physically connected to same network but having same network id):137 I have an 8 port gigabit switch segmented off from our true network to test pfsense. I have 1 NIC from pfsense server going to our real network and the other NIC going to the little 8 porter. I then have a laptop plugged in the switch testing the firewall. Do I need to just unblock these ports? Thnx

I think this might interrest you: http://blog.pfsense.org/?p=149 I usually do it this way.

@fastcon68: I do have the vlans setup up for 2 and 3. I have the opt1 interface and the opt2 interface bridged to the lan subnet. @fastcon68: I really do want to isolate the two vlans away from the other network. I have machines that should only see the wan and nothing else. Do not bridge them to Lan then (did you read the article about network bridging???) Create pass rules for OPT1 to WAN only and similar for OPT2 to WAN. @fastcon68: I have setup the IPSEC rules as well, I can ping the out to the my sites but they can come back my way.  that is cause issues for me.  Any thoughts? Huh, what do you mean? Usually that's the desired behaviour to have a two way communication between IPSec endpoints. …however, on the IPsec rules tab you can control what's allowed in and what's not.

You're running on CF - are you using embedded (the recommended version for running on CF) or Full? Have you verified the hardware (particularly the memory) is good?  A quick run through with memtest86+ (or similar) may be a good idea.  Another useful tools is Prime95 (to check that the CPU and cooling are ok). More details on the "crash" are needed.  At the minimum you need to say whether: a) The entire system reboots b) The entire system hangs and i) You can access the local console ii) You cannot access the local console c) Just the Captive Portal stops responding

@onhel: Might want to take a look at this thread http://forum.pfsense.org/index.php/topic,7028.msg41362.html#msg41362 //////////////////////\//////////////////////////\ Thank you - I so hate the noob level - could a moderator close this post of mine before it wastes too much space - (and time) again - ( cant say it enough) thanks!

Snort 2.7.0.1_3 is the only package I currently have installed. Regards Ben