:) Found the mistake. I installed the HDD with a USB2IDE adapter. And this is a SCSI emulation. The Nokia only kows about IDE, so i had to change the da0… to ad0... -WOlfgang

Ok I guess thats the part I was not clear on. I thought generally you should be on the network you are configuring the rules/addresses for. If I can just build it "offline" so to speak on our old network I can definitely do it ahead of time. I was just worried that if it was not on the actualy network at the time I configured it, there would be issues. Thanks for everyone's input on this. Will report back on how it goes.

Bringing this thread back from the dead, I have switched to yet another system, copied all of the *.rrd files, and while the graphs appear with the old data, none of the new data is appearing in the graphs, including in the system graphs.  The system time is correct, so I'm not sure what's going on. Edit: it would appear the period in which my system was offline, the logging was messed up.  Running updaterrd.sh manually produces: ERROR: illegal attempt to update using time 1251689375 when last update time is 1251697276 (minimum one second step). I believe I'm correct in assuming that just waiting a bit over two hours will cause the problem to solve itself?

@GruensFroeschli: Did you make sure that you dont have an old default route on the "other computer" that's not pointing to the pfSense? There aren't any routes on the computers present. But just solved the problem, seems that the crosscable I used doesn't work completely with a 100Mb NIC, hooked it up to a Gb NIC, and then I could access the webinterface :) @Cry: @bartgrefte: (Hint to developers: make some errormessages, then it would be easier to figure out what's wrong ;) ) Of course, if you can't connect to the console, how are you going to read the error message? Uhm, good point… (Let's just blame the heat for me not thinking straight today ;) ) edit: can't the bootloader give errors before VGA get's disabled?

Following the instructions for FreeBSD should be sufficient.

Update to the latest BIOS.

I went through the setup document various times, and resolved the issue.

Same problem here on 1.2.3-RC1 - as you say, should this be considered a bug? I've been battling to get pfSense installed for over 8 hours today, I feel like throwing the firewall through the window! Chris

Hey Malcolmm, My issues was resolved by low level formatting of the drive before installing pfSense.  Once i did a LLF, it worked flawlessly on a  160GB drive. Frank

HP DL380 G3 and G4 runs well.

Thanks for your reply.  This is what I have MEMORY **[/var/log]cat dmesg.boot | grep memory real memory  = 1072562176 (1022 MB) avail memory = 1035730944 (987 MB) **PROCESSOR  **   [/var/log]sysctl -a | egrep -i 'hw.machine|hw.model|hw.ncpu' hw.machine: i386 hw.model: Intel(R) Pentium(R) 4 CPU 3.00GHz hw.ncpu: 2 hw.machine_arch: i386 [/var/log] PACKAGES bsdinstaller-2.0.2009.0422 BSD Installer mega-package grub-0.97_1         GRand Unified Bootloader iperf-2.0.4         A tool to measure maximum TCP and UDP bandwidth libosip-3.1.0       A low layer of SIP implementation openbgpd-4.0        Free implementation of the Border Gateway Protocol, Version siproxd-0.7.0_1     A proxy/masquerading daemon for the SIP protocol zabbix-agent-1.4.5,2 Application and network monitoring solution Thank you for your help. Finally I have gotten rid of that stupid FATAL ERROR MESSAGE.  All I had to do was to edit /etc/inc/config.inc and change the 32M to 256M now it is working the way it is suppose to.**

I had one other problem getting my microdrive/Atom combo working that may be relevant here. I noticed after much hair pulling that although my CF reader was configured for master (no jumper installed) it would jump to slave after a soft re-boot. I would power the router on USB DVD Rom installed microdrive seen as master, Install pfsense then on the soft re-boot at the end of the install the CF/microdrive would suddenly change to slave. As the install was performed to master it would boot all the way to the mount bit and fail, just like in your case. I think I could still force it to boot by telling it the new location by issuing something like; mountroot> ufs:da0s1b To fix the problem all I did was install the jumper on the CF reader so that the drive was always slave and would not jump about. I also mailed the supplier of my £200.00 board and they said no it must be your CF reader although if you look at these things there is really nothing to them. Just a thought!