Use the embedded image and write it to the cf. You know how to do that from m0n0wall already. If you are keen on the latest test build for 1.2 use this image: http://snapshots.pfsense.com/FreeBSD6/RELENG_1_2/embedded/

Here http://snapshots.pfsense.com/FreeBSD6/RELENG_1_2/

@Odyssey: I booted from the live CD, and installed it to my flash disk using command 99, then placed the flash disk on the MB and was able to get it booted, however after a while in the boot process I get the request to enter a manual root filesystem specification.  <fstype>: <device>when I list the valid disk boot devices I get: ad0s1c ad0s1b ad0s1a ad0s1 ad0 and teh command line says <mountroot>I'm new to this all so what should I do now? which volume do I need to boot and what flile system should I use. tnx for any input :-)</mountroot></device></fstype> use teh ufs:ad0s1a string luke :))) (if you went with default partitioning :))

thanks guys got it working without vlan setup (stupid me)

Yeah, It is working…  :) ---snip--- usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: <ohci (generic)="" usb="" controller="">on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered pci0: <serial bus,="" usb="">at device 15.5 (no driver attached) orm0: <isa option="" roms="">at iomem 0xc0000-0xc7fff,0xc8000-0xd27ff,0xef000-0xeffff on isa0 ppc0: parallel port not found. sio0 at port 0x3f8-0x3ff irq 4 flags 0x30 on isa0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled speaker0: <pc speaker="">at port 0x61 on isa0 ---snap--- thanks.. thorsten</pc></isa></serial></ohci>

No lock up yet on beta3. I have another of these same via boards, I'm going to swap it with my current one now on beta3. I will take the other home install rc2 and see if it also has a lock up. Both of these boards have ALWAYS reported Rx packetloss, FIFO overflow, and receive error (0405) overflow. The console is full of it and I've just had logging off. One of them has been fine doing 20megs for a few months even with these errors. I think its time I ditched this hardware.

sis0 is the default LAN adapter. If it's trying to configure sis0, you must not have saved your interface assignments. I'd go through the assign interfaces again.

That's the known issue currently with embedded upgrades, they'll panic. Don't upgrade embedded right now, there's a ticket open on this.

Don't confuse the boy. If it's got a gz extension or similar, use WinRAR, as you said. If that gives you a useless file, then you probably downloaded the files meant to patch pfsense (like a firmware upgrade) rather than the actual LiveCD ISO. In any case, once you find yourself with an ISO, go and download ImgBurn. It's the best burning (and image creation) tool for Windows and WINE, bar none. Use that to burn the ISO to a disc, then boot up your machine with the disk in, and boot off the disk. Shouldn't case you any trouble at all mate.

@GruensFroeschli: But i disagree with thrusted = LAN and unthrusted = WAN. I beliefe in this concept of a good firewall: The admin defines what is thrusted or unthrusted and set's his rules after this. Not the product defines how the admin has to use it. ;) I'm happy to hear that it's not "hard-wired" as far as the concept of "LAN = trusted" and "WAN = untrusted" goes But it makes sense to me to work within the default params. I'm just glad I could get it to work the way I wanted so easily :) Thanks all!  ;D

thank you Cry, the culprit was the openbsd partition. i rebooted with a gentoo live cd and deleted all partitions using fdisk, pfsense is running beautifully now regards

If you have servers that need to be accessed from WAN it is best practice to move them to a DMZ which means another interface or at least a virtual one if your switch supports VLANs. Depending on how secure your LAN1 and LAN2 have to be it might be necessary to put the network printer in a DMZ as well. Or into a separate DMZ2. VLANs, if supported, might help here as well. But that depends on your network and the ability to change the printer's IP and the user's settings. The latter can be done by logon scripts or policies if you already use them.

Thank you GruensFroeschli. I already did 1-4 before my original post, but I will go through them again and make sure all is still well.  For 5-7, I think that I will wait for the VPN until after the bridge is working.  I don't want to complicate anything more than it needs to be.  It is good to see that the process seems somewhat straight forward though. Our uplink is to a 100Mbps drop in our DC, technically an ISP, but not like what you get at home.  All of the servers (clients) in the LAN need public IP's and do not use DHCP, they are setup as static IP's. Up until now, I have been setting this up in a test environment, but I am going to go ahead and put it into the DC and try to configure it in the final environment that it will be in.  Maybe something locally is messing with it. I will let you know how it goes.

that's correct, but I only have one physical IDE slot on the MB, so that means I can only connect one thing at the same time. I can't connect my flash drive as on an IDE cable since it's a female connector, unless I had a male to male IDE connector, but I don't at this moment, and all stores are closed on sunday. so usb didn't worked… I opened my external laci hard drive to get out the IDE to USB controller and used that one to put the flash disk on, it worked perfectly. I booted from the live CD, and installed it to my flash disk using command 99, placed the flash disk back on the MB and was able to get it booted, however after a while in the boot process I get the request to enter a manual root filesystem specification.  <fstype>: <device>when I list the valid disk boot devices I get: ad0s1c ad0s1b ad0s1a ad0s1 ad0 and teh command line says <mountroot>I'm new to this all so what should I do now? which volume do I need to boot and what flile system should I use. tnx for any input :-)</mountroot></device></fstype>

Also try checking "Use grub" during the boot block installation step.

well I got around the problem.I found that when I run the modem in half bridge mode that this this happens. I am adding the dns servers correctly and all machines behind are accessing the internet fine. I can also download the package list from pfsense. In half bridge its setup to pickup an IP by dhcp on the wan nic and static IP when I set the modem normally. AS far as I can see thats the only difference as the modem still does dns forwarding etc on half bridge.

hi, i suggest us start by cleaning your pc from trojan and other viruses.  then start worrying about your fire wall, if you trojan, i dont think firewall is any good. hadi57

If the router isn't doing NAT then you need to ensure you tell the pfSense host how to find the network behind the router.  In general, anything that can't be found via the default gateway needs a static route set up.  In pfSense this is done from System -> Static Routes.  In your case the Interface would be LAN.  Then provide the address of the network beyond the router and the IP of the interface on the router that's connected to the pfSense host.