Okay I found this:
http://www.freebsd.org/doc/en/books/handbook/network-wireless.html
But as my head is doing the bobb up and down thing from falling asleep at the keyboard I think I better get some shut eye.

Thank you Wallabybob

It's OK for 1.2.3  but captive portal have some pb ? CP is not active correctly

I will test with 1.2.3
I'll give you the result

Thanks

:)
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