Depending on what exactly you're referring to with AD SSO (per-packet basis, implementing such auth on proxy, or…), it may very well be doable for that kind of money. Feel free to contact me to discuss further (cmb at pfsense dot org).

@EddieA: I think the appliance has the VMWare tools pre-installed, and the LAN and WAN are configured for the virtual NICs specified.  But beyond that, I think they're the same beast. Yep. Basically just saves you the step of doing the install, NIC assignments, and making sure you have the right type of NIC (e1000).

That looks like you have your serial console at the wrong speed for the OS. Should be 9600. It's best to change the BIOS so it uses that as well and they're the same.

It varies from card to card and driver to driver, but some combinations are just not capable of automatic link detection. If you assign them manually and set them up, they will likely work just fine.

ok cool, I hope that will be useful to others in the future who need that kind of info :) now im off to sort out installing an embedded image on a DOM YAY!!

yea I was looking at bother actually lol, (yea down time at my job sucks…but hey im being paid so im good ;)) and I am thinking more in terms of going fanless if possible I mean the PFbox just doesn't work as hard as a normal PC so I dont think I need an elabrate system to cool it with...plus its pretty quiet, I have to literally put my head next to it to even hear it honestly...so thats quiet....(and I have hyper-sensitive hearing so if I have to put my head next to it to hear it well that says something....lol)

Yea, last time I saw a 128MB (much less any thing smaller) was when I got my dad off his little 64mb USB stick and switched him to a 1 (or 2?) GB one… but a 4GB card can be had for $12.99 off new egg... http://www.newegg.com/Product/Product.aspx?Item=N82E16820134514 thats the card, grab that for you or your friend or two, one for each of you...and you would be good to go...hope that helps a bit :) if you need a small card the smallest you might be able to find if your lucky is maybe 512mb but they are starting to become "obsolete" as well...1GB minimum is what I would recommend...

1: download the pfsense compressed image from a mirror e.g http://mirror.qubenet.net/mirror/pfsense/downloads/pfSense-1.2.3-RELEASE-LiveCD-Installer.iso.gz 2. extract pfSense-1.2.3-RELEASE-LiveCD-Installer.iso.gz image using peazip or winzip, you should be left with an extracted pfSense-1.2.3-RELEASE-LiveCD-Installer.iso file, dont try to extract this file any further, I think this is where youre going wrong. 3. burn using imgburn http://www.imgburn.com/index.php?act=download or your favourite cd burning program, dont use the windows in-built program, it cant burn ISO images let alone make a bootable CD. if you use imgburn, choose the option "Write image file to disk". Slam

Thanks, that helped.

Not that I've seen, have you tried Firefox on another machine? An extension or any number of other issues could have broken your file upload in Firefox.

You are on ALIX, as you said. That page is for a WRAP. You likely just need a BIOS update, which is also on the doc wiki, complete with a CF image that has the BIOS update on it. http://doc.pfsense.org/index.php/ALIX_BIOS_Update_Procedure

Hi all, similar problem here. First time I try to install a pfSense and i get a similar hang right before booting. The hardware is an ALIX 2D1 (bios 0.99) board which i run with a 512MB CF on which i installed the pfSense-1.2.3-RELEASE-512mb-nanobsd.img using the usual install procedure (dd under linux) After starting the ALIX, i get the bios dump and then the system stalls right before boot: 1 FreeBSD 2 FreeBSD Boot: 1 And the system adds every 15sec. a sharp symbol after the 1 .. I juste installed the 1.2.2 version and it runs perfectly fine!  :-/ I'd be glad to install a smaller version (i.e. 128MB) but the smallest one is the 512MB one. Thanks for help.

So I think I got it working - either one of the following changes (or both) got things up and running on my system. Disabled LBA for the hard drive. Unselected packet blocks during setup. Thanks.

So far so good.  It looks like the checksum thing was it.  Thanks so much for your help Bob.  I really appreciate it! My luck with these things never ceases to amaze me.  The main reason I bought the intel 100's was due to their practically legendary status in the nix world, and then when I go to use them they are one of the broken ones. lol

I have to admit, this is the single biggest gripe I have with pfSense. Many times, I install pfSense inside a virtual machine for testing with no other LAN connected hosts. While you can easily enable SFH via the console window, getting into the web GUI is a different story. In fact, you need a host with a GUI running on the LAN network in order to access pfSense to create the necessary rules to allow WAN clients access to the web interface. ARGH! Luckily, we have an easy workaround.  Here is what do to: Install pfSense  on your target machine Unless your WAN gets a DHCP address, you will need to manually assign the IP Address of the WAN interface:  –> Get to the CLI (option 8 )  --> Type "ifconfig en0 10.20.30.40 255.255.255.248" (substitute en0 for your WAN interface and use the correct IP Address/Mask)  --> Type "route add default <default-gw-ip>"  --> Type "pfctl -d" to temporarily disable the packet filter Point your browser to your WAN IP address then login as admin/pfsense Once you have done your initial configuration, MAKE SURE to enable the packet filter again (CLI --> "pfctl -e") Note - you may have to disable the packet filter a few times because changing GUI options will automatically enable the packet filter. In fact, I just installed pfsense in a new virtual machine today and did the exact steps above. Hope this helps...</default-gw-ip>

@wallabybob: Danswartz: …my take on why someone might be interested in this: Suppose you are on a restricted budget !!! come on, say it…'if you're a cheap skate u might want to do this'...  ;D @wallabybob: and you have a wireless modem to cable or ADSL. You have discovered the limitations of the cheap versions of such modems and have scrounged a system to run pfSense and like pfSense.  But you still need wireless access and because of your limited budget (money, slots, equipment, whatever) you want to know if its possible to use the wireless hardware support in the modem you already have but want pfSense to have some control over the wireless traffic. Well there are many scenarios… I am a cheapskate often <oh dear,="" my="" secret="" has="" been="" exposed="" in="" first="" post="">, but not with hardware. If I have no budget, I go old over good rather than new but crap.  I do prefer minimal hardware and smart config (a bit too much I do admit) too, as this is a way to improve one's code (and waste days aimlessly hacking...). The absolute reason in this case is: I don't want to have a built-in WiFi interface as the box is a ESX host and won't support it probably, pass thru USB would suck and have to be in the DRP.  Another wireless router in addition to the ADSL gateway... no, because it uses more power to load the UPS, generate heat and add ongoing cost and dependability.  (I like to have two of everything- so I don't want 4 commodity routers if instead I can have 2) @wallabybob: Or, maybe you are fairly new to networking and just want to see if you can make the suggested configuration work - as a learning exercise. Indeed. There are a few reasons… @wallabybob: … using the ADSL modem with wireless support would have allowed the wireless connected systems to bypass the pfSense firewall Hmm.  If they were on a VLAN it'd be harder, but yes security here is a major compromise.  For me, the reason is less the WiFi AP. The more I thin about it, the more I'd like to use the Billion's VoIP gateway… for others it might be USB NAS, or VPN... Anyway, you know 'what they say about justifications and statistics!' I'll report again once I can get a decent night's hacking done :)</oh>