Whew! That's what I was hoping for! Thanks to both you guys for the quick replies. Greg

@stantor: I may have found a solution to this. I installed EasyBCD on an windows XP machine. I configured EasyBCD to use an ISO pointed to a location on the hard disk, saved the settings and rebooted. On reboot I got a boot option to go to windows XP or PFSense. On selecting PFSense I was able to load the ISO file and go the menu options to install PFSense. Did it fully install?  Because, if I remember correctly, EasyBCD just alters the boot loader / ini, which pfSense should also try to do on install, either before or after it creates partitions, probably erasing the ISO in the process since it's on the drive it's installing to.  If it even got that far before declaring failure (assuming it detects that it can't mess with a partition that it's in use.) But, let us know if it works.

It also happens if you have a domain names defined in a hosts file, or even on the firewall itself.  Go to System -> Advanced and check "Disable HTTP_REFERER enforcement check" and depending on your environment you may want to check "Disable DNS Rebinding Checks" as well.

podilarius, you hit the nail on the head. I when to "Updater Settings" and set "Default Auto Update URLs" to "pfsense amd64 stable updates", clicked the "Save" button (which set the "Base URL" to "http://updates.pfsense.org/_updaters/amd64"), and everything is GOLDEN! Thanks again!

Thanks for the heads up Steve. My wan is about 20mb/s (download speed) I will do the install tonight on a dual core 2.6ghz system,  it uses just 50watts of power when running, the old P4 box is sucking about 130w!!

Solved, another IT guy had created a new machine on the vmware using the same IP, without checking or updating our static-ip document  :(

pfSense is a customised version of FreeBSD. It is distributed as a complete OS. Do not install FreeBSD, everything you need is on the pfSense CD (or memstick or Nano image). Steve

Hi Steve That's sorted it :) Many thanks for your help and to the other contributors. Best Dude

That sounds a good plan. Backup your configuration before you fiddle with it. Then if you decide you have messed it up so much you can't figure out how to go back you can reinstall, restore the configuration file and be back to a known working configuration.

I don't think you can setup a 1:1 for the same IP as the FW. You can port forward certain ports. I would setup a VIP (IP Alias) on 177.12.170.6 (or what ever) and then use the 1:1 NAT to translate that to 192.168.1.220. Then go and create FW rules. If you only have the 1 IP, then don't use 1:1 but use port forward.

I'm assuming that by 'G' you mean Gigabit rather than 802.11G. Yes, you can use the Linksys as a switch. If, in access mode, the WAN port is no different to any other then use that but I would probably use one of the other 'LAN' ports to be sure. You need to be sure the Linksys is acting purely as a switch or it will confuse things hugely!  ;) Steve

Not easily, no. Even if you could do a gmirror setup by hand (check the doc wiki) it would break the assumptions in the NanoBSD code about the system slice names and such.

ACPI can be disabled through /boot/loader.conf.local which should survive upgrades. See the FreeBSD man page on loader.conf for a description of the significance of /boot/loader.conf.local. See description of loader variable hint.acpi.0.disabled in the FreeBSD man page on ACPI at (for example) http://www.freebsd.org/cgi/man.cgi?query=acpi&apropos=0&sektion=0&manpath=FreeBSD+9.0-RELEASE+and+Ports&arch=default&format=html

Your pfSense box should be in between the uverse box and your internal network (switch, PCs, consoles etc). You should not have two cables connected from your pfSense box to your uverse box. You cannot have the same subnet on the two NICs in the pfSense box. Since the uverse box is using 192.168.1.* you will have to change the pfSense LAN interface as that uses the same subnet by default. Set it to 192.168.100.1 for example. Steve

It would not auto detect the wlan. So I gave it the em0 interface, since that connects to the DSL modem. It appears to have moved on to the next step. So thank you very much for your help. :)

You can install captive portal software directly in the M2: http://coova.org/node/3685 for example. However this does require rebuilding the firmware unless there is an image available somewhere. This still requires an external radius server but would be a two box solution. Trying to run authentication software in a low end router is always going to be tight, IMHO. Steve