What NICs are in use for WAN and LAN interfaces? Instantly upon receiving my package, the port closest to the power input is used for LAN The question isn't about their physical location - but the types of NIC.  At the very least you need to identify the driver or interface name (eg, fxp or fxp0).

This issue has been solved.  I'm not sure exactly what was wrong, after spending so much time thinking it was the software i decided to take my entire network apart and put it back together. After doing this and a fresh install, and setting everything up manually instead of using one of my previus backups, everything works. I'm still not sure what it was but it's all good now.

Sounds to me like your box doesn't support ACPI. http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface

dotdash is correct, you will not be able to assign CARP IP addresses that don't belong to the same range as the interface they're assigned to.  This is a FreeBSD limitation and it causes nasty kernel panics.

@HelloZ: Can I set it up as a switch so that performace is equal to my switch. If you want switch performance you need to use a switch.

With packages you can get this functionality. For this you need to full install and not the embedded version. hardware requirements: http://www.pfsense.org/index.php?option=com_content&task=view&id=45&Itemid=48

You need something with a reverse proxy (hint, search the forum - it's been discussed many times).  I'm not aware of any distro that's designed to do that out of the box.  You'll either need to invest the effort into learning how to do it (probably by following one of the many guides you can find through Google) or pay somebody.

On the console, change the appropriate interface IP to your chosen range using the menu.

Ja, ja, ja! (laughing in Spanish) Sorry I'm a noob on the way to becoming a Guru.

Thanks mhab, but I was looking for an easier way to shutdown. I have a on/off switch on my modem. Thanks dotdash, sounds like a great idea.

@ktims: Script looks good to me, my only suggestion is that you add a couple seconds delay between setting the interface down and back up. I know the Intel hardware is well-behaved here, but I've seen other cards where the PHY doesn't reset properly or at all (link maintained) if you bring the state back up too soon. Updated script.  Good call.  That might save me on a couple of clients where I scraped together a firewall with crappy NICs.

No.

Ah now i get it ^^" Updated the wiki to include the link perry posted :)