Thank you for the replies. I was finally able to install it. It now boots normally. I set the controller to "Compatible Mode" and created a 4 Gb partition for root. I also used a PATA HDD instead of a SATA HDD. Thank you Stefano

i shoul like to do the same maybe this method can work, but i NEVER try it: if is possible to do this: dd if=pfSense-1.2.3-RELEASE-4g-nanobsd.img of=/dev/sdc for "install" the image version maybe can be possible to do the reverse 1. plug the memory or the hard-drive to another linux computer (or BSD? i don' t know..i come from linux) 2. use the command: dd if=/dev/sdc of=/your home cmputer home/ note: sdc maybe can be different someone know if this method can work? i have also found this http://forum.pfsense.org/index.php/topic,9055.0.html

Your title says "no lan card" but what looks to be the pfSense startup clearly shows two LAN cards: em0 and em1. You need to let the startup continue, select option 1) Assign Interfaces to specify which will be your LAN and WAN interfaces, then option 2) Set interface(s) IP address to set an IP address on the LAN interface. Then restart and you should be able to connect to the pfSense web GUI and configure VLAN interfaces. I suggest you leave the LAN interface without VLANs because if you add VLANs to the LAN interface then you will lose connectivity to the GUI when you switch LAN from emx to the VLAN interface and if you made a mistake you will probably have to restart the pfSense system and reconfigure from the console.

@phpzilla: hello  ;D i hope i can help you with my small english  ;) i am a pfsense user from germany and i know your problem exactly. the reason for this boot problem happen in BIOS configuration: 1. open "STANDARD CMOS SETUP" 2. go to "IDE PRIMARY MASTER" or the same in SATA version (SATA PRIMARY MASTER ?) and open it with ENTER 3. switch Access Mode from "AUTO" to "LBA" 4. go back until closing BIOS and answer with "Y" to safe your changes 5. let machine restart and try automatically to start pfsense my background of this problem: i install pfsense normally and all is going good then pfsense will restart and i got this failure like you got. like you i try several ways to clean the failure with no good result. so i try in bios this and that  ::) at last i try to change access mode (phoenix bios) from auto to lba and restart the machine AND IT WORKS ! so i hope it will helps you also to try my way ! greets, phpzilla Yes this was it! You are awesome. Thank you, and thanks everybody for all of the replies. After making that change everything works great now.

@wallabybob: It appears you have some process that starts from time to time but doesn't terminate correctly, hence the available process "slots" are gradually used up. It would be useful to know which process and then determine why it isn't terminating correctly. Please peruse the pfSense system logs looking for error reports from processes. Do you have any packages installed? How long does the system stay up before this happens? Since you system seems to be able to stay up for a day (24 hours?) how about rebooting at the end of the day then in the morning ssh to it give the shell command ps ax and look for duplicate processes (some will be valid), repeat hourly and compare with previous output looking for increasing numbers of duplicate processes.  This won't help it the problem is provoked by a particular "unusual" event which provokes a flurry of creation of processes which don't correctly terminate. You could also scan the forums for topics discussing maxproc to see if anyone else has seen a similar problem. Well, I did some more research and poking around on the router, and I've discovered the problem and fixed it. The issue was caused by NAT reflection. I have a few servers running here, and quite a few people on my LAN, all accessing local servers via their domain name, and it seems the sheer number of connections being created was causing NAT reflection to spawn off too many processes for the system to handle. I disabled NAT Reflection and am working on getting split-DNS set up now. Thank for the advice though guys. :)

thanks for answere, but setting LBA on my BIOS do not fix my problem (i have try 5 minutes ago)

That should work fine. I run something similar at home using a Draytek 120 modem and an Atheros mini-pci card. If you've been using IPFire you'll already be aware of most things to look out for. Like the fact that, unless you put in a firewall rule, your wireless network will be completely isolated from your lan. Steve

You probably need a VLAN capable switch so you can have a "non-VLAN" connection to your internet modem. pfSense supports some USB ethernet interfaces so that might be an alternative way of getting a WAN port. However for not much more than the price of 100Mbps capable USB NIC you can probably get a small VLAN capable switch (e.g. Mikrotik RB250GS)

You likely burned the file to the disc instead of burning the image to the disc. It's a common mistake. Google "how to burn an iso"…..

After several days I "solved" the problem: Either pfsense or the WRAP board is very sensible about long cables (My old router - linksys WRT54GL - worked with the same configuration perfectly). | telephone socket – 1m cable -- Modem -- 20m cable -- WRAP board does not work properly. In my case the connection came up, but pfsense was not routing any traffic (do not ask me why). | telephone socket -- 20m cable -- Modem -- 1m cable -- WRAP board works smoothly. Just in case someone has the same problem...

Hi, thx for reply We are using reflected connections because local servers wasn't able to access other server using the Public IP, only the local IP We need to be able to access Public IP How can I make it works? Tommy Boucher Vice-President Kenotronix Ltée www.kenotronix.com

Is your WRAP on the most recent BIOS version? I have a WRAP and last time I tried it, it worked fine. The WRAP is no longer manufactured or supported by its creator. Given its age, and the fact that the ALIX is a much better replacement for it that is supported, I doubt any heroic measures will be taken to make an "official" wrap-specific image.

There are no amd64 NanoBSD builds (yet, probably not for 2.0). The NanoBSD builds have their own set of features and limitations. They aren't right for everyone. The major differences are: NanoBSD only outputs to serial console (though there may be a VGA variant before 2.0 release) NanoBSD keeps the media read only except for discrete write operations. (This makes it unusable for many packages) NanoBSD has two main OS slices, and one separate configuration slice. Upgrade operations overwrite the currently unused "alternate" slice, and then boot from that. NanoBSD has no installer, it can only be imaged to a disk and run directly. NanoBSD only comes in 512MB, 1GB, 2GB, and 4GB sizes, so using it on HDDs would waste quite a lot of space. Using variable sizes is a non-trivial task. The OS itself is basically the same between the two variants, though there are some kernel differences (a few drivers are left out, like certain SCSI drivers and RAID controllers).

Thanks… it had nothing to do with the interface configuration or deleting and re-adding rules... I think it was ARP cache issue more than anything else...

@dreamslacker: Under Advanced system settings, you can disable NAT.  That will turn the box into a pure non-gateway router. No that's to disable the filter. It also disables NAT, but that's not what you want if you only want to disable NAT. For that, see: http://doc.pfsense.org/index.php/How_can_I_completely_disable_NAT%3F