sometimes rebooting wont be necessary, just disable then enable an Interface will do. its like issuing administrative shutdown and power up to the interfaces.

if you have a spare ps/2 use it, for the sake of installing pfsense on your box.

@stephenw10: The only thing that has happened since is that you rebooted the box, something that I said shouldn't be necessary but Wallabybob recommended. My experience has been that things like moving a subnet from one interface to another and deleting a conflicting subnet from an interface seem to require a reboot to take effect. They are probably not things experienced users do regularly. @stephenw10: Also I can see that I made some assumptions early on that turned out to be wrong. A lesson for me there I think. Often problems are reported with inadequate information so it is necessary to make some assumptions to get started. After a few request/reply exchanges with nothing conflicting with the assumptions its easy to forget that the starting point was assumptions.

@hezten: all 3 options throws me to mount root terminal, even though i hit 3 in the menu (the boot from usb device option) PERHAPS your box has a USB connected "disk device" (such as a SD card reader) that is found on the bus BEFORE the boot device. That would cause the boot device to become (perhaps) /dev/da1 whereas configuration script would be expecting the boot device to be /dev/da0. @hezten: Is there any other way to install this ? I cant seem to get past the mountroot shell / terminal. What is reported if you type a question mark then hit the enter key? You should be able to continue by typing the correct string to that prompt but I can't tell you what the correct string would be since I don't know the device configuration of your system. In the case of you moving a hard drive from another system the boot drive probably changed ints unit number, for example, it might have been  /dev/ad4 in the install PC and then became /dev/ad6 in the target PC. After typing the correct device string to the mountroot prompt the startup should contnue, then when get the console menu type 8 to get a shell prompt then edit /etc/fstab to specify the correct partition for the root file system.

Hi, bgp shows his log lines in System => Routing. you can also go onto console and run config check manually: [2.0.3-RELEASE][root@fw2.jws1.local]/root(19): bgpd -v -n -f /var/etc/openbgpd/bgpd.conf /var/etc/openbgpd/bgpd.conf:4: syntax error <… more errors/config file informations> (on this firewall I have BGPd deactiavated by writing wrong content in ;))

http://redmine.pfsense.org/

WT?! it was this simple all along,I just assumed that it was already iso xD, I wonder if I'll be able to work on pfsense at this level, anyway thanks for your help help man I appreciate it.

Just to add some more information before taking down the internet to try your ideas out. The network cards installed (both WAN and LAN) are TP-LINK TG-3269 http://www.tp-link.com/en/products/details/?model=TG-3269#spec I'll edit this post once I've done my tests. Ok, it was very simple! It was the NIC that for some reason wasn't liked WAN side even though LAN was happy  ??? I swapped the WAN to the onboard NIC and it all started working. Thanks for the pointers and ideas on where to search, much appreciated. Now onto setting up this beast!

Thanks you Steve, work it …..