I have only one WAN and one LAN with LAN Subset 192.168.2.0/24 and 3 PCs on this LAN.

Whilst I agree that shuting down the system with shutdown -h now is the correct way to do this I have never had a problem on any firebox when running Nano. In the NanoBSD install the filesystem on the CF is mounted read only and it runs almost entirely from ram. You could be very unlucky and switch it off just as it was writing some rrd data for instance. I have just found a post from another user who said that he found the console menu could still be accessed but was running at 115,200 instead of 9,600. Might be worth trying that first. Steve

@wallabybob: @spray: Looked up the hardware compatibility list, but could not find "Azurewave Wifi Module". :( Do you want your pfSense to act as a WiFi Access Point? @w00t: http://www.ebay.com/itm/NEW-Intel-4965-4965AGN-wireless-802-11-wifi-3antenna-/390212119080 (http://www.freebsd.org/releases/8.1R/hardware.html#WLAN) For 8$ you get full compability I guess :) Is Access Point mode supported on this card in pfSense? If I recall correctly, Access Point mode is NOT reported in the supported modes of most Intel cards. Ah. Well, the best is to look for cards in the hardwarelist then. Pick one with AGBN and accesspoint-support.

http://ark.intel.com/products/56462/Intel-Desktop-Board-D2500CC d2500cc -> just released this week or so (about last week or so i checked and it was not available yet). Intel board - nice Intel chip NIC (Gb of course) - nice dual port NIC - now that's what made me buying this board 10W TDP mini ITX atom D2500 CPU - not too slow (passmark doesn't have a value for D2500 yet but i expect it to be faster than D525 and slower than D2700, which should still be pretty decent nevertheless) D-sub + DVI PS2 i think it also has one mini express card slot if you want to put wifi card onto it. from what i can see, only thing missing is DC input (see DN2800MT, 8v ~ 19v DC input onboard, very handy) however this can still be over 20W though. i have a intel D525MWV board + seasonic SII 330W PSU (80 plus) + 3.5" hard drive + intel PCI Gb NIC -> all this comes to 30~35W. well if change 3.5" into SSD then maybe it can be close to 20W i guess. alternatively can consider going the DN2800MT route. it is rated at 6.5w TDP but with one NIC only. however the final box would be quite a lot bigger as it'd need a PCI NIC. i bought one D2500CC today together with Aopen S100 case (with 65W DC adaptor). if you don't know what S100 case is, you really should take one second to have a good look at it. currently considering if should buy one SSD or 2.5" HDD - many thanks to thai flood, interestingly, it's cheaper to buy an intel SSD 40G than buying a 320/500G 2.5" HDD… can't wait to get my first pf box running :)

You may also have hit this: http://forum.pfsense.org/index.php/topic,26626.15.html I recent discovered that the ataidle command must be run once per power cycle, and changed the code in pfSense to run that automatically for future versions. It's easy to kill a laptop HDD if the Load Cycle count gets far too high.

Not sure how relevant it would be to that chip, but here is a throughput test from an Atom D510 unit: http://forum.pfsense.org/index.php/topic,27780.msg144750.html

I wouldn't hold my breath on the Cavium actually working with FreeBSD. Their "drivers" for recent versions of FreeBSD do not hook into the crypto(9) framework, if you can even get your hands on them.

In most cases, not so easy. It depends on what you're trying to do, it may not be feasible in some cases and in other cases it may be possible, but not simple.

@larsN: I have this when i writing usbconfig dump_device_desct for my TrendNet tew 645ub Apparently this device s supported by the same Linux driver that supports a device supported by the FreeBSD run driver. But the config output shows a TrendNet Vendor code (0x157e) and it appears that this vendor code is not in the list of supported devices in the FreeBSD run driver. Maybe adding this device's code will be sufficient to get it to work with the run driver, maybe that won't be enough. @larsN: If i buy a wireless card, what do you think about this : http://www.ldlc.com/fiche/PB00066238.html (atheros card, the best from JimP's spread sheet ).. but it's not at http://www.freebsd.org/releases/8.1R/hardware.html Can you confirm ? That card is a D-Link DWA556 PCI-Express card. If I recall correctly there has been at least one reference to that card in the pfSense forums. A search might turn up a report from an actual user. @larsN: I search a wifi card N compatible Pfsense 2.0.1 with an separate antenna , but i don't find. Are you looking for a WiFi card with a detachable antenna and supported in pfSense? The Alfa AWUS036NH appears to have the same chipset as a device I have that works with the run driver on pfSense 2.0.1. I have seen references to this device in the pfSense forums.

The end device is a Verizon router that only operates as an AP. Currently, I am using an over powered (for the purpose) laptop running under Ubuntu 11.10, and the solution works just fine. I connect the Alfa as a client to the AP down the way and then setup up an adhoc connection using the built-in card to give access the house and it works fine. I wanted to just do this same setup using a low end laptop as opposed to my my i7 machine.

I recently built the following[1]. I would go with the Intel dual port server NIC. [1] http://forum.pfsense.org/index.php/topic,44269.0.html

Mmm yes it looks to be a mini PCI-e card however accessing it seems quite an involved process!  ::) Steve

@Hultner: Could you try testing 1/1Gbs Full Duplex. upload and download simultaneously)? Would be grateful. Sorry that currently I am not sure how to set up such a test using Iperf and it cannot be conducted using the client I am using now as it is by the ISP, concurrent test cannot be carried out. In case I managed to make it, I will try to update with you.

I just purchased a new TP-Link modem TD-8840 and seems to work fine now. I think I will stick to the new modem.

Yes, it would be necessary to have a USB drive to run on that, but even with the cost of a USB flash drive included, it is the cheapest low-power device suitable for networking applications that meets the RAM requirement for pfSense.  It would be nice to have pfSense working on a platform this cheap and powerful someday. :)  In my tests, a device with a 400 MHz version of that type of CPU can process more traffic through it (in bridged mode; haven't tested any routing) than an Alix when running the same OpenWrt revision on both (only way I could get the same thing on both). I don't know about the overlay, but uzip could probably be used as an alternative to squashfs, from what I've heard.  Of course, this probably wouldn't be applicable for pfSense, since you wouldn't be likely to have the root fs on the device's own flash memory.

after play a moment with my 3G usb I got a real information about it, my usb 3g is E173s so it did not support current by PF-Sense. and I got something from http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?t=552 # Huawei E173s DefaultVendor=  0x12d1 DefaultProduct= 0x1c0b TargetVendor=  0x12d1 TargetProduct= 0x1c05 CheckSuccess=20 MessageEndpoint= 0x0f MessageContent= "55534243000000000000000000000011060000000100000000000000000000" any body have idea? ??? ???

They're unchanged.

@stephenw10: I expect this machine will now fail!  ::) Excellent, you've taken your first steps towards reducing your exposure to unexpected outages. My process goes something like the following: Assume everything will fail at the absolutely worst possible time. Determine what the worst possible time is for a failure for each service. Determine how all the systems that affect a given service can possibly fail. Determine what, if anything, I can do about the potential failure points. For any potential failure I can't avoid, create a plan of action and documentation for what I will do when it happens.

Hi,   Thanks for your reply! No I haven't done either of those things. I noticed that there is a acpi.ko in /boot/kernel, and I renamed the original file and replaced it with my custom-built one. Probably not the correct way to go about it. I am still quite hazy about the bsd boot process and the difference between builtin "modules", modules loaded from initfs and dynamically loadable modules. As I mentioned in a previous post, I'm more used to Linux. I'll try modifying the boot configuration to disble acpi, then load my custom acpi.ko later on - I guess none of this will really work if acpi.ko really is built into the kernel. The only solution then would be a completely rebuilt kernel. Cheers!

Just upgrade the BIOS and it'll come up after you reboot. No need to reinstall.