Perhaps you should buy the pfSense book.  It's inexpensive and extremely helpful.  I regularly sleep with my copy under my pillow.

Thanks jimp,

Last night I've downloaded the new iso using links (trillion of thanks for including the binary), extracted, compared /etc and I found out I had more then the above two files missing, transferred the files over the installation, reboot and all its fixed.

Thanks again.

Thanks for the advice and the reply!

How much RAM/CPU do RRD graphs (and/or ntop) require?

If I did want to go the ALIX route it seems like they aren't powerful enough…

I might fool around with ESXi but I found a good deal on an alix2c10 that I might also get depending on the RRD/ntop support.

Thanks!

While that list is a good positive indicator (it can tell you which are known to work) it isn't yet a very good negative indicator (it can't tell you what won't work), as we haven't had enough people try others to give data on what does and does not definitely work.

There isn't any built-in way, really.

If your hdd is IDE, you can install the smartmontools FreeBSD package from the CLI (pkg_add -r smartmontools) and then run smartctl -a /dev/ <x>where <x>is your hdd device, e.g. ad0

One of these days I need to make a package/widget for that.</x></x>

It might be clearer to replace sports by includes.

Thank you very much CryHavok for pointing me in the right direction. I have read that post and left a comment.

@Cry:

See this recent thread on the topic.

ver 1.2.3 live cd version

The only way to do it on a single physical interface is to use VLANs.

Documentation is available.

You need to allow 192.168.1.0/30 to talk to 192.168.1.1.  Crossing subnets would require routing which can't happen until you allow traffic in the interface.

Sorry to re-open an old topic, but this behavior has bitten me multiple times….

To clarify, simply disabling the interface (by clearing the checkbox marked "enable ABC interface") is sufficient to prevent config file break-age when deleting a vlan interface?  ???

Or is it truly necessary to go through the entire process of removing any interface configurations before deleting?

Would love to have a steadfast answer on this.

We run a computer shop.  Our firewall and core router is pfsense on a 1.8ghz P4 w/ 1GB of RAM, with 5 physical interfaces, one of which hosts 16 vlans.  As workbench areas change, the network config often needs to change.  I would love to be able to add/remove vlans as needed without fear…. had to rebuild the box once over this before I learned how to restore the config by hand.

Thanks folks...  Great system otherwise.  Wouldn't run anything else...  Love it.

Edit:
Running release 1.2.3 with 2.0 dashboard installed.

Most of these use Supermicro boards (Intel NIC's), so if you didn't want to build it yourself it's an option.  Plus you get a warranty on the whole thing.

http://ironsystems.com/items.asp?Cc=ACLASS

It doesn't look like any of the apt caching programs have a FreeBSD port, which pretty much rules out any chance of a pfSense package.

If you raise a bounty, somebody may take it on.

There are some anchors in the ruleset for this purpose, and some packages do add/remove their own rules in various ways.

If you know how to use pfctl to do this directly, it should work.

DNS dnsmasq 7372 reading /var/dhcpd/var/dhcpd.leases

Holy Smokes! It worked!!!

Gob was right with our modem, It was acting as a router with no dhcp enabled so I followed jimps advise and everything is working now!

Thanks so much guys for all the help!!!