thnx for ur help.

Freebsd doesn't like your cdrom dive/controller. Some of the messages can be ignored if it works (at one of my systems I get the read_big_illegal_requests too but it works), however your system is not able to boot up completely. Try setting your bios to pio mode for the cdrom drive (disable UDMA modes). Also see http://wiki.pfsense.com/wikka.php?wakka=BootOptions how to disable dma for atapi drives. If nothing helps try with another cdrom-drive.

Oh, and next time don't shoot your image with such a high resolution  ;)

Hi Hoba,

I am using FireFox and I also downloaded through Net Transport. I also tried different mirrors an I will try to extract it with a different program to extract the file.

Greetings, Marcel

I am now using WinRar and Nero is not complaining any more and I also found an posting about this:

http://forum.pfsense.org/index.php/topic,2636.0.html

Greetings, Marcel

I left the Motorola SB5100 modem unplugged for 10-15 mins and tried again. Same message. It does not get an IP address.

I tried going to the modem page by going to 192.168.100.1 and copied the mac address down. I put than on pfSense and still the same issue. I don't get any IP address.

I have noticed in the past that when I plug the SMC router into the modem, I initially get ip 192.168.100.10. Then when I release and renew, the modem learns my routers mac address and assigns me the real IP. If I clone the modems mac on the SMC router then I get the real IP without getting the 192.168.10.1 address first.

Is there any one using pfSense with RCN Cable Internet?

My magic ball is broken.

Post the contents of /tmp/installer.log after the failure.

Use diagnostics -> Edit file from the webConfigurator to get the contents of the file.

ok

np  ;)

Hoba tx a lot. You made my day :D Couldn't understand why it wouldn't work after RC3…

what did you do , because i'm having the same problem since upgrading to 1.0.1

I understand that IZarc is the problem here and like I said I was able to get it to work using the latest winrar.

What I was asking for is a md5 hash of the ISO file itself INSIDE the .gz file that we download.
I checked the md5 to see that all was right, but I can't burn that file so it was useless for me.

It comes down to not being able to verify the integrity of the file you need to burn.

Inclusion of the md5 hash of the actual ISO file that we need to burn in the future would be helpful.

Thanks

Then scott is right.

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