Also, is pfSense compatible with Serial-ATA hard drives?  i've tried installing on serial-ata hard drives & the 99 install completes just fine.  But after rebooting, pfSense or FreeBSd gets got in a loop, continuously scrolling some messages on screen.  i can't tell what messages because it goes by too fast. They are supported but this issue is caused by FreeBSD 6, only happen on some chipset/motheboards combination it is fixed on 6.3 and better.

Can someone please give me a step by step to do what was mentioned here? once you're up and running you'll need to use Diagnostics -> Edit File, open /etc/fstab and change ad0 to ad2 or however it shows on your ALIX. Save that file and reboot to test, and you should be set. I have an ALIX setup and running just fine but I cant for the life of me figure out how to change my fstab. Currently it wants to boots from ufs:da0s1a and I have to type in ufs:ad0s1a when I reboot this is from installing to an adapter card. When I go to Diagnostics -> Edit File, no matter what I type in nothing happens and the screen stays blank. Thanks ahead of time.

Is it possible that your CF card s just very slow on writes and the installation would eventually finish if you wait long enough?

iv set it to boot from cd and iv even unpluger the hard drive but it still does not see the disk is there some other way to burn it on to the disk to make it run?

see http://devwiki.pfsense.org/wikka.php?wakka=BootTroubleShooting grub might fix that, among other possibilities there. Please report back on what you find.

The core developers have been working very hard on the upcoming releases pfSense 1.2.1 and 1.3. Today I was work on 2 phone systems so I've also been very busy. I believe the package url is: http://files.pfsense.org/packages/ Can you manually see the location from behind the firewall? I just installed squid on my  pfSense 1.2-RELEASE built on Wed Apr 23 21:04:50 EDT 2008. It installed fine. This could have been a routing issue on the internet. Try the package install again and see if it is working now?

Looks like you plugged the hard disk into a different socket on the motherboard.  Try moving the swapping the cables around.

http://devwiki.pfsense.org/FlashHowtoScript

Hi! because I make some script to schedule restart service, create captive portal file, and something. But I do not want to edit or copy every time I install the Pfsense, I want to make an iso to add some changes to. Pls, help me.

Thanks for the feedback.  This is just a test box using what I had on hand.  I prefer intel nics but I would be hard-pressed to fault the realteks in this case.  I think they should be removed from the HCL.  Simply enabling promiscuous mode shouldn't cause a meltdown like this.  I looks like a freebsd driver issue though and not a pfsense specific issue as far as I can tell.  I just feel bad for anyone using an onboard 8169 in a small form factor setup. Paul

@dutler: yes, i would say that is rather ugly :D are you doing anything else with the debian host? nop :)

Hallo! OK, I tried to disable all, but no change. Might the instaler be incombatible to the motherboar chipset? ais

If you are trying to use the autodetect function you first need to unplug all cables from the nics and then plug each cable back in one at the time when prompted.

If you configure your clients to use pfSense as DNS, you can configure the DNS forwarder accordingly. I assume you have a domain for your network. On the DNS forwarder-config page is the part: Below you can override an entire domain by specifying an authoritative dns server to be queried for that domain. So you could set your internal DNS for your own domain.

Thanks for the help. I think I have a good idea what I need to do now.

Never mind I downloaded untangle and got it working. I do think PFSense is excellent but will use it in some equipment from one of the recommended vendors.

At the command prompt, sysctl net.inet.ip.ttl=128 (for example) will work. I am not sure if this setting is exposed anywhere in the web interface. It won't persist across booting - putting the default value in /boot/loader.conf (in which case it would be net.inet.ip.ttl=128) is one way around that. Note - unless this setting happens to be somewhere in the web interface (in which case don't touch the sysctl), this is unsupported. Change things at your own risk.

Thank you for the resoponse :).  I was trying pxe because i was having issues with using CF (whole other off topic issue I won't go into).  The only reason i was curions about NFS was because i had no other way to test NFS, aside from loopback on the server itself. Agreed about the FreeBSD boot process.  It looks like this fails when init starts correct?  I think that normal versions of FreeBSD will grab rc.conf at this point, but it looks like pfSesnse (via m0n0wall) has done away with the typical method.  Someother time for me too, I think. Thank you!