Great news thank you for your answers.. Thanks "rhy7s", i dunno this repository and will download the latest one, and thanks "Perry" the post of "jimp" achieved to convince me, so i will go with 1.2.3 !

Thanks for your hint!

Well I can describe how I did it  :) I set up af TFTP server on a Debian machine and then booted the Soekris (5501) from that machines NIC. There are many guides on the net describing how to setup a TFTP server. Iam not sure this is the easiest way but it worked perfectly for me. I guess the easiest thing is to mount the harddrive in another machine, install PfSense on it and then put it back in the Soekris.

fitted new cf card and it just booted straight up :)

@GruensFroeschli: I'm confused. Is the pfSense OPT IP 192.168.118.1 or 192.168.118.100 ? Or has the server this IP? You wrote contradicting things. Thanks for replying. The Problem is solved. After an reinstallation I was able to add another l-Adapter (le0,le1,le2). In my old installation (VMWARE Download from pfsense.com) the Name of the adapter was em0 Now I'm happy  ;D

Problem solved, now everything works like a champ. Thanks to all that helped.

You can't (yet, that's been added in 2.0) short of maintaining aliases yourself.

I have what sounds like the same Kingston CF, and using the 4 GB image works perfectly. Not to mention about 40 other various CF cards. The looping fsck is bad, that would indicate file system corruption. I've only seen that on images where the build process went awry, that hasn't happened for months though.

@pfsense_fan009: Is it normal the writing to a CF could take more then 20 minutes? Depends on how fast your CF is and how fast your writer is. With an old USB 1.1 writer it can take a lot longer than that. With a good USB 2.0 writer and a decently fast CF, 10 minutes or so is about what it takes for 2 GB.

The disk usage will never grow on embedded (unless you start making modifications outside the web interface). Things like logs are all strictly in RAM. It'll sit there at whatever it's at now forever. So you don't need to upgrade thinking you're running out of space, you won't. Getting on the nanobsd embedded (1.2.3-RC3) is preferable so you have the current supported, upgradeable embedded. But there is no impending issue because you're low on space (you were to begin with, that hasn't changed).

@dotdash: b) The embedded kernel output to serial by default, it is no longer available as an option in 1.2.3rcX. I just saw from another thread, that strangely, the embedded kernel can be installed from the easy install, but not from the custom install. I missed that, as I haven't tried an easy install in some time. Perhaps it will get added back to the custom install.

different subnets is a must, nothing silly.

I don't recall the "7 option pfSense menu". What does that look like? (It would probably be sufficient to show a couple of the options.) Since your system doesn't have a video interface (and presumably no video hardware) its probably best to use the embedded kernel to avoid invoking a driver that thinks there is a VGA device in the system. If I recall correctly, the default settings on the pfSense serial port are 8bits, no parity, 9600bps so you would probably want to change the BIOS settings to the same values so there is a "seamless" transition from BIOS control of the serial port to FreeBSD control of the serial port.  I would expect that if you are using the embedded kernel you wouldn't need to invoke BIOS redirection because the booted boot loader and kernel shouldn't be doing any video output of its startup progress.  (But I've never used an embedded kernel so I have no personal experience of this.)

Thanks, it was the firewall rule that was missing.  I thought when Opt1 was bridged to the LAN it would automatically pass all the protofcols/etc.  Should have read further.  That part was in the documentation I was reading I just didn't get that far into it… premature configuration.   :-[  Once I did that it started working great. I appreciate the specific rule for DHCP above, for now I'm opening all the ports "any" for the Opt1 / wifi interface as I want the wireless clients to be able to access other devices on the LAN without restriction. D'oh on the dual radios, I wrongly thought I could use an A/B/G card to operate on all bands, but I should have known that wasn't the case.  I understand why, just didn't really research that part or think it through.  Not a big deal as I'm just using it for home as a test. All in all seems to be working well. /Posting from a Wireless client.

Well help is always appreciated, but if people would search and use the existing documentation there would be less time wasted on duplicated efforts and reinventing the wheel. I could understand if there were some deficiency in the existing instructions, or if they were out of date. However, in this case, if he had looked up the issue on the Documentation Wiki, he wouldn't have needed to do all the research, writing, and so on. It's already been taken care of and kept up-to-date. Also, we try to discourage people from downloading images from unofficial or non-developer sites for security and integrity reasons.

yeah, i noticed that.  i'm not sure how that explains my not being prompted for the slice though?  it did prompt me (if i recall) until i replaced the /boot/kernel directory.  oh well, i don't much care at this point, i now have the packages git repo and a booting nano install in virtualbox, so i can actually get some work done :)

You said you have seen the problem on a PC with onboard "re" LAN. Suggestion: Put your cards on that PC. Install or boot pfSense. At interface configuration time specify you want to use VLANs and configure two VLANs, one for WAN and one for WAN. At the later prompt specify option 8 to get a shell prompt. Then type dmesg | more which will display the startup output a screenfull at a time. Use a digital camera (or phone) to capture the who startup output and post it somewhere we can look at it. I suggest using pfSense 1.2.3-RC3 or one of the RC3 snapshot builds to get the most up to date hardware support. Here's an example of sartup output showing an attach failure which resulted in the device not being available. (This is to give you an idea of what to look for.) re0: <realtek 8168="" 8168b="" 8168c="" 8168cp="" 8168d="" 8111b="" 8111c="" 8111cp="" pcie="" gigabit="" ethernet="">port 0xd800-0xd8ff mem 0xf7eff000-0xf7efffff,0xf7ee0000-0xf7eeffff irq 18 at device 0.0 on pci4 re0: Chip rev. 0x3c000000 re0: MAC rev. 0x00400000 re0: PHY write failed re0: PHY write failed re0: MII without any phy! device_attach: re0 attach returned 6</realtek> I believe in this case the problem was fixed in a later version of pfSense.

There are some "modern" alternatives anyway: DiskImage http://www.roadkil.net/program.php?ProgramID=12 or https://launchpad.net/win32-image-writer/+download

Are you trying the embedded install? What if you try a vanilla FreeBSD install CD?