uupps  :-\  Sorry for double posting …  please delete

If you use 1-1 NAT, then everything is forwarded from the external IP to the internal IP. You just have to open the ports you want in the firewall. If you use port forwards, then you would just add the VIPs, and select the correct external IP from the drop-down when creating the port-forward.

Cool, thanks Issue closed!

I just used other drives I had available- the 1U servers sometimes have the same caddy as the laptops. You can also swap the drive in the caddy with another laptop optical drive, but the mounting holes have to be in the same place.

Bloody hell. I just realized that I didn't download the right update. Great. Time for a full reinstall.

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.