Well, I figured it out.  It just works.  Installed pfsense and loaded up the m0n0wall config file.  It said…upgrading m0n0wall to pfsense...and it worked.  Simple as that.  It would have been nice for someone to just have said that...but...oh well.

@cmb: 1.2-RC3 was released last night and is VERY close to what will be 1.2 release. It's by far the most stable version available. i found it after post my message… :) I don't know why RSS feed wasn't updated, so i didn't know that a new upgrade was available.. anyway, i create a new topic under "NAT" forum.. i hope that issue will be solved, maybe i found a little bug in /etc/inc/filter.inc thanks :)) k.

Make sure DNS on the firewall is working.

You can install to the microdrive using any machine, then move it into the WRAP/ALIX. Either with a IDE to CF adapter, or booting a machine with a USB CF writer. I typically do the latter. Can also use VMware's USB redirection.

Depends on which version you use. If you have a full PC with hard drive, use the iso and you'll have VGA output. If you have an embedded board with a CF slot, write the embedded image to your CF and the display will be on the serial console.

The problem was that the system wouldn't get past loading the kernel - but it is moot now, since I've ordered some microdisks to use in the system instead. :)

Tried changing that setting but all the ones I tried jumbled up the post settings too, so I don't think it's that setting.  Anyone else have any ideas? Edit: NVM, I changed the conspeed on the soekris to 9600 (which apparently is the speed required for pfsense) and I can now access the console.

Glad you're here!  ;)

It was broken around 1.2 RC1-RC2. Should be fixed now, there are new embedded update files which seem to work fine for everyone.  try it out. http://snapshots.pfsense.org/FreeBSD6/RELENG_1_2/updates/ There is one known upgrade issue with a Lighttpd bug, if the webGUI dies when you try to upgrade, use the console upgrade via SSH. see also: http://blog.pfsense.org/?p=149

Thanks,  I will start to search for AP's that allow "Allow intra-BSS communication" to be disabled.

You should run the single processor kernel. Embedded disables some things (like DMA) which you do not normally want to disable on a full PC, but typically have to be disabled for things to work on embedded hardware. There is no measurable performance difference between any of the kernels. They all have largely the same options.

Not likely that anything has changed since earlier this year, I wouldn't recommend trying.

You need to do a full install to the CF like you would a HD. The logs still aren't just going to pile up forever though, they're still rotated long before they get anywhere near 100 MB. If you want to do a full install to just keep more logs locally, that's not going to achieve what you desire.

No, the documentation is outdated. Use 1.2RC2.

@Master: Any particular thread in mind? I already searched the forums, but I could not find anything relevant concerning a recent (FreeBSD 6.2 based) USB installation. I know, that booting something from USB has always been kind of problematic, and I never played around with it (mainly due to the lack of a large enough USB media), but I assume it should be possible somehow. Many, but basically it comes down to the fact that consumer grade flash memory (which includes CF cards and USB disks) will "burn out" with a sustained write load.  The embedded install is designed with this in mind, but the full install isn't and writes merrily to the disk. @Master: Still a good question, because I have no clue, what a full installation needs "2 GB hard drive or larger" for. I am actually running a full installation on a machine with a 18 GB softraid-1, and this is what the discs are used for: <–-SNIP---> So even with some packages installed, we are far away from the specified minimum hardware requirement for harddrive size. Is it possible, that embedded & full installation just have the same memory requirements nowadays? The embedded install is a fixed size - no packages.  The full install is a variable size that depends on the packages you install and the size of the logs.  I suspect 2 GB was picked as a reasonable upper limit on what people would require.  My 4 GB microdrive (of which only 3.2 GB is usable) currently has about 0.5 GB used.  By this point a 1 GB unit would be looking a little too small for my liking.

There's a problem right now with an apparent bug in Lighttpd where it chews up a bunch of memory and dies during upgrades. If you run into this, the console upgrade will still work fine. I actually like console upgrade better because you can just paste the URL in and it downloads and upgrades automatically.

Well - you don't want to run two devices with the same IP/Netmask so what you need to do is bring up the system without connecting the lan side to the network where the 192.168.1.1 router is - then use the "Set LAN IP Address" selection ( selection 2 ) and set the IP address to something that is not assigned on the 192.168.1.0/24 network - set the netmask to 24 and save the settings - then you can connect the lan interface to the 192.168.1.0/24 network and access the pfSense server using http://{the IP address you assigned to the lan interface here} (without the {}) and you should get a login page. Make sense??? gm…

did you change the webgui of pfSense to another port?

Impossible for us to help without posting system logs.