Ok, thanks. I'll try a temporary configuration with an unused routable C class to test all this before using it for real. Maybe when I'll be ready for that, the 1.0 final will be out  ;D

You might be able to use linux to dd an image direct to the embedded flash although good luck upgrading it afterward - heh.  Hopefully the unit(s) load the OS into a ramdisk after booting, if not, I can't see how you're going to dd over the on disk OS w/out panic'ing it, resulting in an immediate paperweight. If possible, I'd do the following. Boot into linux configure the flash to read-only (better yet, see if you can put the OS in a ram disk and change the / mountpoint to it - good luck) SSH into the machine use ssh to ssh to another unix box passing dd if=pfsense.img of=/dev/whatevertheflashdriveis command to the remote ssh daemon Pray that nothing writes to disk other than the dd, sync; sync; pull powercord - do NOT let the OS hit that disk power on and pray some more If it works, pay me $1000 for the consulting and report back.  If it doesn't work…do the same ;-P --Bill

@hoba: Please try to disable serial console at system>advanced, save and turn it on again, save. Then reboot. Does this fix the issue? I tried this on a IP330, it get's to the same point as the other poster said.  I tried what you suggested.  Still getting the same thing.

Thanks for your quick responce i wasn't sure if it was a known bug or not. I have gone back to beta2 for the moment will upgrade when the new snapshot comes out.

okok, seems to have a problem with the modem.. Btw, pfsens rocks ! thanks to it team for this work :) regards, ronan.

yeah, I think that's what you want. you can dump your monitor now  ;D

Thank You!

I think we are now crossing threads.  Please do not do this.

Then make a seperate subnet for the wlan. captive portal can't be enabled at a bridged interface.

At which point does it refuse to start or crash or whatever? What is the last output you get before it stops?

This used to be a problem with older versions but is no longer an issue with beta2.  Atleast not with usb memory sticks.  I wouldnt trust a floppy as far as I can throw it.

Keep in mind that only thr wrap has 3 LEDs. Other devices like the soekris only have an "error" LED to toogle and this then might confuse a user. Also the Wrap LED is solid green before freebsd actually starts booting. This might also confuse as you can't tell is it hung before trying to boot or is it up and running. But if it can be done like in the following example without breaking something for other platforms that don't have the second LED I would like to have it too: 1st LED is always on (at least for the wrap, indicates Power, you can toogle it but it might confuse due to the above described reasons) 2nd LED is off before BSD starts booting up and switches to blinking state when BSD takes over. It will finally switch to on when it's up (same time when the readybeeps are played)

@sullrich: Try running it again.  I fixed this a bit ago. Thanks, I have updated again.  I am still on "RELENG_1_SNAPSHOT_03-19-2006" is this correct?

Try the packet mode option. I need to set it for my cf-cards in ide-adaptor too.

_Edit:  I worked on this for two hours last night before posting and going to sleep.  This morning it's working normally again:  local hostnames from DHCP are resolving, lease infromation is being written to /var/dhcpd/var/db/dhcpd.leases, and they show up in the web interface again.  Several reboots last night made no diifference. _ Perhaps I spoke a little too soon.  When I installed from LiveCD, I made sure to not create the swap partition and I read the FAQ about changing /etc/platform to "wrap".  It still did not create a memory file system, everything was mounted RW and it was writing log entries.  I didn't find any of the scripts in /etc to reference PLATFORM of "wrap", so I changed it to "embedded", but that didn't change anything. Having figured out the CF IDE adapter, I decided to just put the BETA2 embedded version on it.  No problem getting it to boot up and work but something's not right with the DHCP/DNS. The web GUI refuses to show any leases any more, though there actually are several.  The local DNS seems intermittent now.  It worked fine with the install from the LiveCD. Some lease information is being written to /var/dhcpd/var/db/dhcpd.leases~ but not to dhcpd.leases.  Note the tilde. Here is output of mount" mount /dev/ufs/pfSense on / (ufs, local, read-only) devfs on /dev (devfs, local) /dev/md0 on /tmp (ufs, local) /dev/md1 on /var (ufs, local) devfs on /var/dhcpd/dev (devfs, local)      <–-- Is this right? /dev/ufs/pfSenseCfg on /cf (ufs, local, read-only)

@hoba: Maybe you should compare bios settings and bios version then as you are running the same hardware. What I did was I tried defaulting the BIOS to standard and performance settings, but neither one worked. Playing around with IDE controller settings mode no difference either.

Usually 99 should be able to kill existing partitions but I would give erasing the disk and removing all partitions before a try. It's evil Linux  ;D For the keyboard issue, once you have the livecd up go to the webgui and enable ssh at system>advanced. You can use ssh to run the installer or other console commands too. (be aware that creating keys will take some time depending on your cpu speed before ssh is started). This is not really aa solution but a workaraound.

@shavano: It just doesn't recognize the CF at all.  There's no "ad0" in /dev, so neither of the commands work at all.  The drive is detected by the BIOS and by the version of FreeBSD in m0n0wall, just not by the 6.1 in pfSense and not by 6.0-RELEASE. This is a FreeBSD issue then.  You will be better suited to raise the issue on a FreeBSD related list so that it can be possibly fixed.