Well if it were a fresh install it would have it built in, and wouldn't show up under pkg_info, and does not need installed separately. The issue you're seeing is that a package, when removed, took rrdtool away with it.

Also, i'm on the latest BIOS update for that mobo and the RAM is totally fine (Dell RAM, Dell mobo, Dell latest BIOS). I don't get errors when I boot any other OS on that system??? I'm wondering if I should be worried about a possible failure coming up on one of the memory slots (since swapping out the memory produced same result) - or if possible there is something else wrong. or should I just ignore?

@Jarhead: I only have 256M RAM, could this be the reason?? I doubt it. I have a Jetway motherboard with VIA CPU and 256MB RAM and it runs pfSense "Full" version just fine. @Jarhead: I can boot m0n0wall fine and I can boot the memstick version of pfsense but I cannot boot the 512 version. So why are you trying to boot the "512" version? @Jarhead: I get a Fatal trap 18: integer divide fault while in kernel mode. Then it says cannot dump. Device not defined or unavailable. FreeBSD writes crash dumps to swap file. If the kernel crashes before there is a swap file established (e.g. early in the startup if you are running the "full" version or anytime if you are running the nano BSD version) then the kernel has nowhere to write the crash dump. @Jarhead: This is with the vga 512 version, with the plain 512 version it never gets past the Verifying DMI pool. Its a while since I watched a pfSense startup and "Verifying DMI pool" doesn't appear in the recorded startup output of my system (output of dmesg pfSense shell command). "Verifying DMI data" is BIOS output?

@jimp: I added that to the doc wiki as an faq this morning… wish I knew why it wasn't going away, since it's in the obsolete files list and should be removed automatically by the upgrade process. Were you perhaps running the Dashboard package on 1.2.3? Nope.

Since pfSense is a firewall there are no compiling tools included, make gcc etc. It would only be an additional security risk. If you need to compile for pfSense 2.0 you do it from a standard FreeBSD 8.1 install. However, as tommyboy suggested, there are precompiled binaries available for many packages which can be installed directly to pfSense. Steve Edit: Looking through the packages it looks like there may only be OCI8 clients available.  :(

Thanks, i already removed most of the config files content and then i restored it manually.  :(

Thanks,i will try this once i receive my cable to use a 40gb 2.5 inch hdd on my router hardware.

That early in the boot process it's way into FreeBSD territory - probably nothing we can do there, but if you can find a BIOS update or tweak some BIOS options, especially ACPI, it may help.

2.0 asks you half-way through the boot process whether or not you want to install.  Reboot, keep an eye on it, and press "I" when it tells you to. As to your CF RAID, whether or not it works really depends on what chip powers it.

I've given up - after a few fresh-installs, new creation of new VM and "pain in the head" log file reading I'll wait till  pfSense gets an update - maybe then it will work. Actual FW is m0n0 which indeed is very good, but I'm missing pfSense features ;-)

Exactly what I needed. Thanks a million!  ;D ;D ;D

That seems to have worked.  I'm in the GUI now. Thank you.  Strange with no errors that it would be different the second time around, but I'm happy it seems to be working now.

There are some posts in the same way. Getting All I saw people trying, Try this: change sata mode in bios retry install burn another media in low speed install 1.2.3 and upgrade

Ok. You have answered my question.  I downloaded the wrong file.  I'll now download the correct file. To answer Bruce, I have a HP Pentium with 1G of RAM a disconencted harddisk (as Public IP does not need it), 2 NIC cards and the other normal bits and pieces you find on a motherboard that is 5 years old. The outcome I want is to have pfsense replace my ZoneCD from PublicIP, which looks like is no longer in existense.  My wife has a 40 seat Cafe in which we offer free wifi for our customers with 2 and data caps per day per user. Wouldn't mind a hand with that but I'll search the form for help, unless you can point me in the right direction. Peter

RESET STATES…Fixed it. Thank you. I had tried the rules for the 192.168.1.x networks before but to no avail... but that was because I never "reset Firewall states".    Once I did that it was all working . Thanks again.

Updates don't happen with pfSense but every so often any way. Usually on the order of a year plus between updates. Officially released updates anyway. You can pull from GIT, but I would only do that if it fixes a certain problem you are actively having.

Thank you so much for the clear and informative answer :) I dunno what I'd do without pfSense!

Sorted :)

@Jason: Can I just create entries for those on the System Tunables page? No, loader variables are not the same as sysctl tunables.

@bainwave: Thanks bob for your speedy help. few more questions still hunting me.. 1. I have  CISCO Catalyst 2950G switch, can I club all my 3 broadband connections with a single NIC? if yes, how could I achieve this? All my broadband connections are having a pool of (20) public ip's. 2. Now can i configure all my public ip's into this pfsense in order to run my show? Am in a work group environment, can I control the users & computers from this pfsense? Once again Thanks for your advise. You need to setup VLANs on pfSense upon the first boot up.  Configure 1 VLAN each for the 3 WANs and 1 LAN. If for example, you use VLAN 10, 20, 30 and 100 for WAN 1, 2, 3 and LAN respectively; then you continue with the interface setup assigning VLAN 10 for WAN, VLAN 100 for LAN; the remaining interfaces can be configured from the webgui. Let's assume you use ports 1, 2, 3 on the switch for WANs 1, 2 and 3 respectively.  You'll then need to configure Port 1 to be native VLAN 10, Port 2 to be VLAN 20 etc.  Now, these ports need to strip the VLAN tag on egress and tag on ingress (default VLAN ID per port). Next, assuming Port 4 is connected to pfSense, you'll need to trunk VLANs 10, 20, 30, 100 to Port 4. The rest of the ports that are connected to LAN will then need to be in VLAN 100 (tag on ingress aka default VLAN ID) and strip the VLAN tag on egress. eg. In priviledged access mode type: vlan database vlan 10 WAN1 vlan 20 WAN2 vlan 30 WAN3 vlan 100 LAN exit copy running-config startup config configure terminal interface fastethernet0/1 switchport mode access switchport access vlan 10 interface fastethernet0/2 switchport mode access switchport access vlan 20 interface fastethernet0/3 switchport mode access switchport access vlan 30 interface fastethernet0/4 switchport mode trunk switchport trunk allowed vlan 10,20,30,100 interface fastethernet0/5          <–--  repeat bolded section for all the ports you need to be on LAN switchport mode access switchport access vlan 100 end copy running-config startup-config After that you can configure the remaining VLAN interfaces in pfSense for your WAN2 and WAN3 links accordingly.