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.

FreeBSD does not have Xen support in FreeBSD 6 just yet.  I am not sure this is going to be possible until 6.2 or 7.0.

http://www.pfsense.com/bootdisks/

well i got the part that you solved the problem… What language are you translating from?

Yes, we are planning on fixing this.  Perhaps if you are in a hurry to get this fixed you can jump in and help us finish it. These things don't write themselves, afterall.

Thanks for the reply, no they are not connected to the same switch, my setup is as follows: Internet <->Modem <-> WAN NIC <-> LAN NIC <-> SWITCH <-> LAN PC's I changed the setup so that both NIC's are on the same subnet and it appears to be working again although I was dropping packets all the time but after a few restarts it came right (may of been DNS caching or something?), anyways this should do for what I need it for. Now I just have to try to figure out the traffic shaping! Thanks.

The 64MB image works.  Resizing it to 512 is what did it. :\ I suppose I could go back and re-calculate the sectors I made it grow and try it again.  Really wish there were a way to automate this, or just create a clone install of arbitrary size, a la Carbon Copy Cloner for OSX.

Check the main site - BETA 2 is out… http://www.pfsense.org/index.php?id=22 UPDATE: pfSense 1.0 BETA 2 posted! We are proud to announce the availability of BETA2. Countless fixes and a lot of work went into this release. Get it at your nearest mirror. Thanks to everyone who has been helping us by reporting and diagnosing bugs. ;D 8)