I download and copying the dom.so from php52-dom-xxx package. Do not use other package like php5-dom-xxx Bye  :D

@cenriq: Is there any way to do remote administration on the system? That's what I am searching on now. Thaks for your support. As dotdash stated, enable SSH and HTTPS under Settings->Advanced in the menus. What he didn't mentioned was that you MUST add firewall rules on WAN tab to allow incoming connections on these ports.  To reduce SSH brute force attacks, you might want to change the default SSH port from '22' to say..  '222'. If you do not want to reveal HTTPS on your WAN, you can always do a SSH tunnel socks proxy on the client then access the HTTPS webgui via the LAN IP.

That was me  ;D The snapshots update far too often to be effectively mirrored without wasting a ton of bandwidth. Once 2.0 is released it will be a moot point. It normally isn't an issue that too many people are trying to access snapshots at the same time, since they're generally for testing. But 2.0 snapshots are just too good to pass up!

Ok, my friend. Thank you.

Have you tried a pfSense 2.0 snapshot build? Sometime newer software works better with newer hardware. A while back I had trouble usb USB devices on a motherboard with AMD 780G chipset and snpshot builds of pfSense 1.2.3. A few months later the problem didn't happen with the released version of 1.2.3.

I've found two possibilites: After initial installation, first time you enter to webui and go through the wizard or in the webui System->Routing and there is first the first tab, after that don't forget to take it in use

I need a workable solution to install 2RC1. Help please?

I rolled back the bios and still continued to have issues. I followed the boot troubleshooting doc but nothing helped. I've also been getting a number of other errors during the install, so I've decided to give up on this machine. I grabbed an even older IBM server that I had laying around and got pfSense up and running on it in no time at all.

In the Web GUI, go to Diagnostics/Command and type in the following in the Execute Shell Command box dmesg | grep -i smp If the SMP kernel is installed, you'll see some resulting text.

doesnt seem to matter what I do. i get the invalid mount option message every time i try to install 2.0 to a sata disk drive. tried putting the drive in an old machine and running delpart and fdisk /mbr to completely wipe the partitions off the drive and redo the MBR. did not help at all. im kinda stuck at the moment. I dont have access to a MAC  to try that method but it seems the delpart and fdisk /mbr should have worked. any other ideas? or am i just gonna be hosed and have to use a flashdisk module or SSD or something? [edit] it actually does not matter at all which type of disk i use. flashdisk module, IDE hard disk, SATA hard disk. I get that error message about invalid mount options. how do i fix this? FreeBSD 8.2 installs no problem so im not sure how to proceed. [2nd edit] I have discovered that MY particular issue came from attempting to install from a USB CD-ROM drive. the drive is detected and the install begins, but during the hardware detect/driver load phase in the boot process of the installation, it fails to work. if i plug in an IDE CD-ROM the installer works as it should. just a heads up there. bug i guess. trivial bug.

@Cry: NanoBSD (and embedded) use the serial console, not VGA output. I'd suggest you try that, with a serial console cable, before you try modifying images. If I use the hacom pfsense 1.2.3 nanobsd and then upgrade to the new pfsense 2.0 though the update feature do I need to access the console by serial cable first to assign the NIC again or I just use GUI. Current I don't have a serial cable, do you think will this work?

For the logs, 2 versions : one w/ the original configuration, another w/ only the first serial port enabled Now, w/ pfSense v2, "sio" ports were renamed "uart" pfHacom boot logs Still haven't bought serial port pci cards + null modem cable but, one friend gave me still his "usual packge used to configure various branded routers" : still a USB/DB9 cable + a DB9 cable (which i suppose null modem). Still the same problem : Putty (or any other terminal client) keeps blinking on the upper left corner but w/o any interaction possible… Thank you

Thanks for the rapidity. I think that I will test the version 2.0 because the PC just has one network interface. Thanks too for the French forum link ;)

I had the same issue on an Alix 1C. Managed to solve it just now. http://forum.pfsense.org/index.php/topic,20405.15.html gave the answer. Set the power management from ACPI to APM and it should boot up normaly now. Update 1: Turns out http://doc.pfsense.org/index.php/Boot_Troubleshooting also listed the above solution. Apparantly the Alix boards with Award BIOS haven't been working for a while with BSD. – Nephi

We run pfsense on an IBM x3250 M3 without any trouble.  We did however run into some issues with the graphics card on an x3550 M3 when we installed Fedora on it a few years ago.    To fix that I used the vesa graphics driver by adding xdriver=vesa to the boot options.  I'm guessing thats not the issue with pfsense though since there is not a gui. Found this on the freebsd forumns - http://forums.freebsd.org/archive/index.php/t-6022.html

Start here and then go looking for a file called pfSense-2.0-RC1-i386-YYYYMMDD-HHMM.iso.gz Where YYYYMMDD-HHMM is a date and time.