Just do the regular installation using a live ISO. but keep in mind that you shouldn't install services like Squid to create massive read/write on the card as it will poot! One more thing you need to consider is package management. dont try to install more than one package at the same time as it will create write errors at next boot and the package management will fail itself. hope it helps.

Should be alright. Give it a whack.

hi don't want to minimize the write access, i want redirect it to the hdd thx

Sorry for the mistyping in fact is pfsense, Im changing from m0n0wall to pfsense because it is more flexible and complete. Ill try your sugested configuration.

For the uVerse 2Wire routers yuo have to have the WAN connected to the 2Wire DMZ set up as DHCP, which is sounds like you did. pfsense also can manage multiple Vlans on a single NIC. Look in your interfaces to see if there is a vlan with the 172 set up on that nic

Consider bridging your LAN and WAN interfaces.  This will turn pfSense into a filtering bridge and should do what you need.

Unfortunately both of the howtos you linked are contributed and aren't on our Wiki or I could update them rather easily. I did add a note here: http://doc.pfsense.org/index.php/Port_Forward_Troubleshooting#Common_Problems About needing an IP bypass for a port forward to a server behind a captive portal.

Several older copies of the config are kept in /conf/backup/ So if you get dropped to a shell prompt because something didn't work at boot, you could always pull one of the 25-30 or so backup configs from there.

Just install pfSense onto the new hardware and restore the config. It may ask you to reassign interfaces but aside from that, as long as the number of interfaces is the same (or greater) there shouldn't be any issues.

It would probably be possible to compile pfSense for it, but it likely doesn't have enough flash memory to store the OS or enough RAM to run it.

problem solved !! Thanks Jimp !!! :)

Found the problem! I had exported a config file from another system that had a few packages installed on it. Since the packages weren't installed on the new set up, the config file couldn't find them! I removed this from the confg file and the errors disappeared!

Either your BIOS is broken (it should allocate distinct memory address ranges to each PCI device) OR it is erroneously configured to boot a 'plug and play' operating system (doing its own PCI device resource allocation). pfSense (FreeBSD) assumes the BIOS will do the PCI resource allocation.

I've looked on the Freebsd site and tells me to use the ATH driver as it works with all Atheros except the AR5005VL chipset. "HARDWARE     The ath driver supports all Atheros Cardbus and PCI cards, except those     that are based on the AR5005VL chipset. A list of cards that are supported can be found at     http://customerproducts.atheros.com/customerproducts/default.asp." http://www.freebsd.org/cgi/man.cgi?query=ath&sektion=4#end Could some please tell me how to go about using the ATH driver instead of the required one for AR9220? Thanks in advance

You're right. But today that's the only way I found to install pfsense on Cf using a Jetway barebone, because nanobsd image written to Cf doesn't work fine for me: it doesn't complete the boot on that hardware or it doesn't configure right the serial port. If in the future vga support will be included in the nanobsd image, I could get more info on the problem. In addition I don't exclude It could also be a serial port configuration error I did. Nanobsd's serial output only is a problem when thing doesn't work fine and debug informations are needed. Thank you again for your support Jimp Greetings from Italy Borgo

Thank you very much Havok you make me very happy So my installation is correct and my CF memory is safe: root file system is read-only and /var and /tmp are on ram

You can also do it without touching your cables. More than once I've matched device names with the NICs by viewing the FreeBSD Release Hardware Notes. This also works for FreeNAS and m0n0wall. You can search for your specific NIC or browse the list of NICs under 3.2 Ethernet Interfaces. I've used FreeBSD release 7.2 here: http://www.freebsd.org/releases/7.2R/hardware.html#ETHERNET Some kind soul has also created a shorter list that is quicker to use: http://networking.ringofsaturn.com/Unix/freebsd-polling.php

The instructions were just gathered/added from various sources over time, indeed the block size isn't relevant aside from performance. That's the first I've noticed that actually. We'll clean that up.