I have option B (cisco) running and so I definitely recommend that. :)

Yes, as clarknova said it's already installed.  Just go to VPN/OpenVPN in the GUI.  Also, there is a forum dedicated to OpenVPN here… http://forum.pfsense.org/index.php/board,39.0.html

using RELENG_1_2_3_RELEASE commit seems to solve the problem. thanks.

If space is at a premium, Netgate ( http://netgate.com/ ) has some outdoor cases and even some marine gear I think, that would let you mount a router pretty much anywhere (above the water line) and save some space that way. :)

@EddieA: I currently run pfSense as a VM on ESXi. My cable modem goes to one NIC, on the ESXi server, where the pfSense WAN is the only VM connected.  The pfSense LAN goes to a separate virtual switch, where other VMs connect, and also to a second NIC, and a physical switch, where the rest of my network is hooked up. I'm quite happy with this setup, and it works perfectly well.  But, as can be seen in another post here, I just picked up an HP Thin Client, where I'm going to run pfSense, to sit between the cable modem and "relegate" the ESXi server to being just another machine on my network. Cheers. This is what I plan to do.  Maybe in the future run a physical box.  Are you using this method as solely a firewall?  Any other features? tnt

Mister wallabybob: I've installed the system PF Sense to the stage for a final gave me wan -192.168.0.13 and 192.168.1.1  lan -worked prepare for because 192.168.0.10. Knowing that I am currently working Maikarotik system. But when I open the browser and type the IP Address 192.168.0.10 does not open my pFSense. Note that the local network there by a yellow triangle. A. In your opinion, why not call and thank you

@clarknova: I was hoping to catch a lead on cheaper PCI expansion. $80 on ebay Sorry, can't help there.  Although, when I was looking, by trying different search terms, I did find others selling the expansion, and I seem to remember one Canadian, I think, seller had a bunch, at around $25 each, although right now I can't find it again.  Here's a cheaper one: http://cgi.ebay.com/PCI-Expansion-Module-Hp-Compaq-t5720-Thin-Client_W0QQitemZ330390809465QQcmdZViewItemQQptZLH_DefaultDomain_0?hash=item4cecd3ab79 That's exactly why I waited for a box that came with one already installed.  I paid less than $80 for the complete setup. Cheers.

We're very open to feature requests in general, but in this case if you're going to request the ability to add on top of a stock FreeBSD release, that's going to go to the "needs patch" pile, i.e. it's not going to get any attention from us. pfSense is a customized OS in itself, there are a few dozen patches to FreeBSD to make it behave better as a firewall and router. The rc system would break everything on a stock FreeBSD. For those reasons, amongst others, we won't ever have the ability to install on top of a stock FreeBSD. There's just way too much difference between the two for that to be remotely reasonable.

To build images and such, yeah, those steps work great – but that's done from a FreeBSD box these days and not from within a "Dev ISO" environment.

This is really embarrasing.. it was just an broken nic… so i bought a new one and it works like charm! What confiused me was the fact that i could ping from pfsense to my pc but not the other way around but what wireshark told me that the wan interface was pinging me... so i switched the network cables... en i could go to the network interface!! Thnx!

Thank you all for the suggestion I had a very drastic approach: I built a spare firewall with new mobo, new HD and new NICs. I loaded pfsense 1.2.3 and my configuration. In office non-working hours I plugged in and tested / stressed for few hours with no problem at all from various workstations. I even increased the download speed to 15/20 MB/sec (depending from the OS of the workstation). Yesterday I definitively changed the firewall with the new one. The old firewall (Pentium III 800EB + shuttle mobo) has been on 24/24 from 2001, working as a PC, as a little server, as a Winroute server, as a monowall firewall and lately as a pfsense server. It still seems operational, but probably the NICs have suffered most. Max

There is no way to duplicate a nic card. They are physical cards in the machine. I'm not sure I'm following what you're saying you did.

I submitted this as FreeBSD problem report i386/144045. Thanks, Darin Peshev

oooh  :( we only have our FX5622, we will try to boot from a multicard reader in a standard PC, when I'll get it, I'll let you know. Many thanks!

@Augustino: I want to know how is working pfsense with this server, mainly detecting 2 networks cards Broadcom 5722 1GbE Single Port NIC Are there some issue with sata harddrives? If it works with FreeBSD 7.2 it will work. @Augustino: Are there some issue running over vSphere of vmware? Countless people run in production that way, and much of our development and testing is done in ESX, works well.

Thanks, :-) will try to get it working this week. :-D

Why not use a free ESXi from VmWare to do all this??? Very easy to manage and configure….

Update: I have added the line vfs.root.mountfrom="ufs:ad0s1a" to /boot/loader.conf and it now works fine. Can anyone give me some clue as to what is actually going on here? This box is a new model that I suspect many people will buy. There MUST be a better way to install than this? Thanks, Chris PS. Instructions to install that work for me: Run LiveCD with a blank USB stick in the front. Select install to Hard Drive. When asked, select the hard drive ignoring the USB device. When it asks about the boot blocks, disable packet mode. Disable everything on the USB stick as it is not needed. When the device reboots at the end of the installation, power off and remove the USB stick. Power back on. It now boots but stops and asks for the root filesystem. When prompted enter: "ufs:ad0s1a" Follow normal install process. Once it is running edit (either through the UI or through the shell) /boot/loader.conf and add the line:   vfs.root.mountfrom="ufs:ad0s1a" All Done! YMMV

Oh, jeez.  I gathered you could only have the serial access by installing the embedded version.  Thanks for the quick reply.