Backup the config from your running system (diagnostics>backup/restore). Copy the config.xml up to a floppy or usbdrive (msdos formatted) to "/conf/config.xml". Then Bootup the Livecd with this media attached. The system will come up with the old config that was loaded from the media and will be useable immediately. Then run Option 99 to move everything over to the hdd (system will still be useable while doing the install). After it finished it will have a short downtime for the reboot. This way you only have downtime for 2 short reboots.

thanks,

problem fixed with full reinstallation

Use firefox.

I'm not certain; it appears to execute twice in my system logs (relevant lines below)…

...
Welcome to pfSense 1.0.1 on the 'embedded' platform...
...
Executing rc.d items...
Stopping /usr/local/etc/rc.d/dnsmasq.sh...done.
Stopping /usr/local/etc/rc.d/olsrd.sh...done.
Starting /usr/local/etc/rc.d/dnsmasq.sh...done.
Starting /usr/local/etc/rc.d/olsrd.sh...done.
Bootup complete
...
Dec 31 19:23:33 dnsmasq[545]: started, version 2.22 cachesize 150
Dec 31 19:23:33 dnsmasq[545]: read /etc/hosts - 4 addresses
Dec 31 19:23:33 dnsmasq[545]: reading /etc/resolv.conf
Dec 31 19:23:33 dnsmasq[545]: using nameserver 10.0.0.1#53
Dec 31 19:23:35 pftpx[613]: listening on 127.0.0.1 port 8021
Dec 31 19:23:35 pftpx[613]: listening on 127.0.0.1 port 8021
Jan 1 00:23:37 php: : Create RRD database /var/db/rrd/opt1-traffic.rrd
Jan 1 00:23:37 php: : Create RRD database /var/db/rrd/opt1-packets.rrd
Jan 1 00:23:37 php: : Creating rrd update script
Jan 1 00:23:37 php: : Creating rrd graph index
Oct 31 21:48:07 php: : Resyncing configuration for all packages.
Oct 31 21:48:07 dnsmasq[545]: exiting on receipt of SIGTERM
Oct 31 21:48:07 dnsmasq[741]: started, version 2.22 cachesize 150
Oct 31 21:48:07 dnsmasq[741]: DHCP, IP range 10.138.1.10 – 10.138.1.254, lease time 5m
Oct 31 21:48:07 dnsmasq[741]: DHCP, IP range 10.130.1.10 – 10.130.1.254, lease time 5m
Oct 31 21:48:07 dnsmasq[741]: DHCP, IP range 10.0.0.130 – 10.0.0.250, lease time 2h
Oct 31 21:48:07 dnsmasq[741]: read /etc/hosts - 4 addresses
Oct 31 21:48:07 dnsmasq[741]: reading /etc/resolv.conf
Oct 31 21:48:07 dnsmasq[741]: using nameserver 10.0.0.1#53
Oct 31 21:48:09 olsrd[750]: Adding interface ath0
Oct 31 21:48:09 olsrd[750]: New main address: 10.130.1.1
Oct 31 21:48:09 olsrd[750]: Adding interface sis0
Oct 31 21:48:09 olsrd[750]: Adding interface ath1
Oct 31 21:48:09 olsrd[757]: olsr.org - 0.4.10 successfully started
Oct 31 21:48:09 dnsmasq[741]: exiting on receipt of SIGTERM
Oct 31 21:48:09 olsrd[757]: olsr.org - 0.4.10 stopped
Oct 31 21:48:09 dnsmasq[762]: started, version 2.22 cachesize 150
Oct 31 21:48:09 dnsmasq[762]: DHCP, IP range 10.138.1.10 – 10.138.1.254, lease time 5m
Oct 31 21:48:09 dnsmasq[762]: DHCP, IP range 10.130.1.10 – 10.130.1.254, lease time 5m
Oct 31 21:48:09 dnsmasq[762]: DHCP, IP range 10.0.0.130 – 10.0.0.250, lease time 2h
Oct 31 21:48:09 dnsmasq[762]: read /etc/hosts - 4 addresses
Oct 31 21:48:09 dnsmasq[762]: reading /etc/resolv.conf
Oct 31 21:48:09 dnsmasq[762]: using nameserver 10.0.0.1#53
Oct 31 21:48:10 olsrd[764]: Adding interface ath0
Oct 31 21:48:10 olsrd[764]: New main address: 10.130.1.1
Oct 31 21:48:10 olsrd[764]: Adding interface sis0
Oct 31 21:48:10 olsrd[764]: Adding interface ath1
Oct 31 21:48:10 olsrd[767]: olsr.org - 0.4.10 successfully started
…

Example contents of shell script files:
#!/bin/sh
cp /root/foo.conf /var/etc/
killall foo
sleep 1
foo -z /var/etc/foo.conf &

Thanks,
-Pete

@syntax:

I can only imagine that with the plethora of 1U racks without CD's flying around (like the Hacoms) that there would be some form of regular demand for this.

Your forgot one more option. These devices can boot over ethernet. There are even prebuild VMware machines that you can fire up as server to boot the livecd over ethernet. Haven't tried this yet but it might be worth a try.

Quickrun through the community vm's:
http://www.vmware.com/vmtn/appliances/directory/74
http://www.vmware.com/vmtn/appliances/directory/371

Problems have gone after a fresh reinstall of pfSense…

Seems as if there's something weired going on with the update ;-)

Should not need to access the console again after a upgrade.

Thanks Scott

??? ??? ???

Really sounds funny to me…

I also had a lot of ... not trouble ... but questions ... but that is normal with a "not stable" firewall version < 1.0

But now REALLY nearly everything works

thanks to scotts and bills high speed patches  ;) <<<

FTP helper ? Thanks for it to be there but you can surely switch it off and open up your ports, but why do you want a firewall then ?

Perhaps use the IRC or forum and there are surely some guys that can help you… ?

A very very very happy pfSense user

yip reboot has fixed sip logging and appears to have fixed the time.

its a pc engines wrap i am pretty sure its 128 MB.

Also check out http://wiki.pfsense.com/wikka.php?wakka=BootTroubleShooting

FAQ.  Please search before posting.

http://faq.pfsense.com/index.php?action=artikel&cat=4&id=89&artlang=en&highlight=m0n0wall

Thanks for the clarification.  I figured ALL the files/binaries were self contained within the tarball but your explanation makes sense (and I can see why that would not be the case)  :)

My apologies Hoba.  I will keep it in the mailing list.

If it runs on the native hardware but won't work inside the vm on that hardware this is a vmwareproblem. I'm using vmware server with pfSense on athlon64, dual PIIIs and centrino systems without problems (only for developement and testing). I think there is nothing we can do at the pfSense site to fix this.

The swap partition is optional. If you put enough ram in the box you won't need it. Of course enough ram depends on load and used packages.

Or simply reinstall / reflash.

Reinstall / reflash.

Thanks.. i have now just installed the system using option 99 from the livecd menu.. everything work just fine :)