Should be fixed in 1.2-BETA-1.

@MrPK:

…
Or shoudkl I use the http://snapshots.pfsense.com/FreeBSD6/RELENG_1/updates/pfSense-Full-Update-1.0.1-SNAPSHOT-03-27-2007.tgz ?

Yes, that one.

Correct.  The board is based on a 815 intel chipset.

Have tired updating the BIOS but can't find an update! :)

Any help greatly appreciated.

Try booting a FreeBSD 6.2 CD on it, I'm guessing it won't work. If the CD boots, try doing an install and see if it works.

This is a FreeBSD bug, the only way this problem will get fixed is if you could do the test with FreeBSD and if it's still an issue, post back here. Someone can help you get the appropriate info to post to a FreeBSD list to get this resolved.

Not really (at least not when it comes to the blank local console). It you attach your WAN and have some nonsense subnetsettings that conflict with your LAN or some DHCP at WAN that assigns conflicting settings with your LAN you might end up with a broken webgui/network at LAN though.

@rrbranco:

:)  :o  :)

I'm really astonished by the quality of the your project, it's stability, potential, quality and "simplicity" (related how easy to use it is, not related to developing / maintaining ) .

As I could read on the forum, almost each and everything was foresaw, analyzed and treated.

Great work, congratulations.

Thanks a lot.

Regards from Rio de Janeiro - Brazil.

Rodrigo Ristow Branco

Thank you!  :D

Sorry Hoba should of looked there I did think about it but I decinded not to.

444 days is my biggest uptime (just checked, 2 machines of a carp cluster). You can schedule tasks by adding them to the schedules section in the config.xml (download it and have a look at the very bottom of that file). Add your reboot command there, upload it again and it will trigger the reboot. Not sure why you need it though.

In fact, there were no reason to change anything else than the hash in the config.xml …
Comments are WELCOME. :)

./script_to_change_passwd.sh pfSense-1.0.1-Embedded.img

** Changing pfSense-1.0.1-Embedded.img password !
** Default hash password : $1$dSJImFph$GvZ7.1UbuWu.Yb8etC0re.
Enter new password :
jgjhg
** Hash of the new password : $1$UTy1VPBC$72d69mEhlGnPlYB2YMkgB.
** Creating the device entry ( /dev/md<> ) …
** Image file device: md0
                <password>$1$dSJImFph$GvZ7.1UbuWu.Yb8etC0re.</password>
** Change has been made. Congratulations ! :-)
** Removing temporary directory
** All done.

Here is the code :

#!/bin/sh

This script has been made to change the root/admin password without launch pfsense usage : ./script then you will be asked for the password

DEFAULT_HASH='$1$dSJImFph$GvZ7.1UbuWu.Yb8etC0re.'
IMGFILE="$1"
WORKDIR=pwd

fonction_error_occurs() {
cat << EOF

Error : Default Hash Password ( pfsense ) Not found …

You should :

Download the lastest image file from www.pfsense.com gunzip mdconfig -a -t vnode -f mkdir tempdir mount /dev/md <number>tempdir Have a look to tempdir/conf/config.xml to retrieve default password Write it into this script at line 5 Advertise other users ( pfsense forum or whatever you want )

EOF
echo "** Now safely stoping ..."
umount $WORKDIR/d
rm -rf $WORKDIR/d
mdconfig -d -u ${MD}
echo "** Done"
exit 1
}

echo "** Changing $IMGFILE password !"
echo "** Default hash password : $DEFAULT_HASH"
echo "Enter new password :"
read PWD
HASH=$(php -r "echo(crypt('$PWD'));")

echo "** Hash of the new password : $HASH"
echo "** Creating the device entry ( /dev/md<> ) ..."
MD=mdconfig -a -t vnode -f $WORKDIR/$IMGFILE
echo "** Image file device: $MD"

mkdir $WORKDIR/d
mount /dev/${MD}d $WORKDIR/d

grep $DEFAULT_HASH $WORKDIR/d/conf/config.xml ||  fonction_error_occurs
cd $WORKDIR/d/conf/
cat config.xml | sed s/'$DEFAULT_HASH'/'$HASH'/ > config.xml.2
mv config.xml.2 config.xml
chmod 640 config.xml
echo "** Change has been made. Congratulations ! :-)  "

echo "** Removing temporary directory"
cd $WORKDIR
umount $WORKDIR/d
rm -rf $WORKDIR/d
mdconfig -d -u ${MD}

echo "** All done. "</number>

What are the specs of your box? 50% CPU for pushing 100 Mb likely isn't high at all, depending on the CPU and NIC's in your firewall.

Thanks to those who have helped out so far.

I don't know if what I just did is good news or not:

I put the flash card in a Dell GX110 instead, and did an installation onto the flash card.  It took a little time, but it went through without a problem.

I took that flash card, and put it back into the GX260 and it booted up.  I walked away from it for a little while, and I had the following message on the screen when I came back.

ad0: timeout - write_DMA retrying (1 Retry Left) LBA=5665679

I'm thinking the GX260 doesn't like something about the flash card, or something is still enabled in the BIOS that I don't see.

I rebooted the GX260 with the flash card and disabled the DMA and ACPI again.  I'm gonna keep watching it and see if the error comes back.

that forum thread contains no info - the link is unaccessible :(
when mouting pfsense install image on a TFTP i get this

kernel.jpg
kernel.jpg_thumb

@Tenzen:

for those interested: http://tenzen.dnsalias.net/soekris

the link doesn't work - asks me for a password  >:(

This was fixed long ago in recent snapshots and if you search you will find:

http://forum.pfsense.org/index.php/topic,2864.0.html

Your LAN computers should be set to obtain ip automatically. If the line is static, you can just set the WAN on pfSense to static and plug in the numbers. It is possible that the Nokia is running PPPoE or something. Ask the DSL tech and set the WAN accordingly.

Yup, I'm building one of the FX5620 boxes and it doesn't have a CDROM and I don't have a USB one to boot from.  While I can pull the disk and built it elsewhere, it's a lot of effort compared to doing a netboot from a trusted interface.

Try upgrading the bios. if it is a bios problem there is no way we can work around this.

Packet mode (from man boot0cfg):

packet  Use the disk packet (BIOS INT 0x13 extensions) interface,
                    as opposed to the legacy (CHS) interface, when doing disk
                    I/O.  This allows booting above cylinder 1023, but
                    requires specific BIOS support.  The default is `packet'.