Not off hand at the moment but this may be possible soon. I'll repost here if I ever swap the box out.

ARP cache induced problems are very common when switching firewalls, power cycle the router upstream of your firewall if you have access to it, and also any DSL or cable modems, if applicable. You may be forced to call your ISP, or wait a few hours for the ARP cache to clear.

It's standard port 80 HTTP traffic. It's not possible to use a proxy at this time, it's on our wishlist so hopefully it'll get implemented at some point.

Well, I got my IP back at least tonight. And the box is bootstrapping as I write - it's probably going to take a while. I don't think that poor old P-II 400 mhz cpu is really up to the task in a speedy manner, or so to speak. I think perhaps the HD was in a bad shape, because I couldn't get the machine to start the bootstrapping .. I swapped out the HD with another one, and off it went. So, obviously I am on a 1.2 router right now. Let's hope the connection stays up. I probably won't fiddle around with the traffic shaper this time, since that was when my problems started the last time I was on a 1.2 system… Hopefully I can use Project Evil and get the WLAN card up and running as well, following the guide I posted a link to above. Oh, and obviously I didn't consider the fact that the bootstrap process would also update the software of the router ... So sorry for my confusion about the BETA-1 developer image. ;)

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.