Update your BIOS:

http://doc.pfsense.org/index.php/ALIX_BIOS_Update_Procedure

It should work then.

It will prompt you to re-assign the interfaces when you restore the config. Should be easy.

It should work fine. Upgrading a config from 1.2 has worked flawlessly for anyone I've heard try it.

Thank you for that.

I run my PFSenses in VmWare….. I gave up on the X335's. Ran it on the X345 and it worked great, but i needed the easy admin of Virtual Center Server... It is easy getting to the console via encrypted VPN, so I chose that way of doing it. Never going back....

After searching through google, it was recommended to replace the RAM. I did so, and have been up and operational since.

Somebody going by the name of 'jimmy' was working on some LED code, but I haven't heard any updates.
http://forum.pfsense.org/index.php/topic,14315.0.html

Before you edit, run:

/etc/rc.conf_mount_rw

Afterward, run:

/etc/rc.conf_mount_ro

/libexec/ld-elf.so.1 and  /lib/libc.so.7 are missing.

You need to either re-create the symbolic links or reinstall the package.

In either case, you should see if the devs of rtorrent can help you.

Apparently the image files are too large to get a proper bsdiff of when uncompressed. I tried it on two different boxes which each had enough RAM to hold the images in memory at the same time and it still failed.

I did a diff of the original gzipped image and a patched equivalent. The patch is larger than it should be though, due to the original image being signed when the patched one is not, though it's still quite small (272 bytes).

http://pingle.org/files/wrap-512.bspatch

@cmb:

@mayoryusa:

2nd) for my captive portal server..it always show cpu usage 100% when the server up for more than 3 days… need to restart

What is taking up the CPU?  Paste the output of top.

how to do?

Sorry, should've been more clear.
I've tried different versions of pfSense only to find one that would work, which was a 1.2.3 RC1 release but somehow the filesystem layout for this one was so messed up that I couldn't do an upgrade. All of the other versions either wouldn't find the boot loader (No /boot/loader found) or would boot but would end up missing the root filesystem.

I've eventually tracked down the problem I think:

If you're trying to write the image file to a CF disk from an OS X machine, OS X will try at random intervals to mount that image making the disk unavailable until you click "Ignore". Because of this, the whole writing to disk fails but you don't see that from the output. (I've tried using Disk Utility to burn the image to the CF card but that one borks as well saying the image is corrupt)

I've eventually been able to write a 2GB image (1.2.3-RELEASE) to a 4GB flash card from a spare Linux laptop I have lying around and that worked fine so the end result is that OS X keeps trying to mount a device (or at least do something with it) that messes up the writing of the disk image.

Not sure yet how to be able to write an image from OS X without it trying to mount it continually but I'll figure that one out sooner or later.
At least, now I've got a working pfSense machine.

Sorry about the confusion but this was really strange.

Regards,

Jeroen

I'm now in the process of compiling my own pfSense image. I hope I can fix it in the developer img, and then rebuilt the ISO with the modified kernel.

I'll keep you folks posted on my progress 8)

Hy! I had issues with pfsense when I try to connect from putty.
I use hypperterminal from windows.

serial setting 9600 8biti on the client, not pfsense(there should be com1 or irq4 set up in bios), and use a normal serial modem cable.

The understanding that pfSense is not a package but a complete installation - you can't install it on top of FreeBSD (or anything else).

your welcome, I try when I can (or think I can)