Hi cps, I confirm to you that I had to reinstall all packages which had web interface (like "lightsquid" for example). Thanks for your confirmation. I hope this post will help other users.

Also, this motherboard doesn't appear to be listed on the Jetway website, no bios upgrades.

push edited the script one post before this Efonne, maybe you can additionally link this from the script thread? Thanks!

Thank you dotdash, I can meanwhile confirm that you are correct :-)

Based on the builder code, to use this with a nanobsd image simply replace /dev/${MD}d with /dev/${MD}s3 in the mount command to reference the proper slice for the configuration.  These scripts will only work for a full image, not an upgrade image.  Note that you must use gunzip to decompress the image before using any of these scripts. Modified script for nanobsd (also modified some parts to be less potentially destructive and work with absolute paths): #!/bin/sh # This script replaces the config file in the # image with your specified config file. # Usage {configfile} {imagefile} # Example ./replace_conf.sh myconfig.xml pfSense.img NEWCONFIG="$1" IMGFILE="$2" echo "Image file: $IMGFILE" MD=`mdconfig -a -t vnode -f $IMGFILE` echo "Image file device: $MD" mkdir ${IMGFILE}.mnt mount /dev/${MD}s3 ${IMGFILE}.mnt cp $NEWCONFIG ${IMGFILE}.mnt/conf/config.xml chmod 644 ${IMGFILE}.mnt/conf/config.xml echo "Replaced config with $NEWCONFIG" umount ${IMGFILE}.mnt rmdir ${IMGFILE}.mnt mdconfig -d -u ${MD} If the new config should be the default when you reset to defaults, the config file should be placed at /conf.default/config.xml in the OS slices rather than /conf/config.xml in the configuration slice of the image: #!/bin/sh # This script replaces the default config file in the # image with your specified config file. # Usage {configfile} {imagefile} # Example ./replace_def_conf.sh myconfig.xml pfSense.img NEWCONFIG="$1" IMGFILE="$2" echo "Image file: $IMGFILE" MD=`mdconfig -a -t vnode -f $IMGFILE` echo "Image file device: $MD" mkdir ${IMGFILE}.mnt mount /dev/${MD}s1a ${IMGFILE}.mnt cp $NEWCONFIG ${IMGFILE}.mnt/conf.default/config.xml chmod 644 ${IMGFILE}.mnt/conf.default/config.xml umount ${IMGFILE}.mnt mount /dev/${MD}s2a ${IMGFILE}.mnt cp $NEWCONFIG ${IMGFILE}.mnt/conf.default/config.xml chmod 644 ${IMGFILE}.mnt/conf.default/config.xml umount ${IMGFILE}.mnt echo "Replaced default config with $NEWCONFIG" rmdir ${IMGFILE}.mnt mdconfig -d -u ${MD} To make an update image from the first OS slice of a full image: #!/bin/sh # This script creates an update image from a full image. # Usage {imagefile} {updatefile} # Example ./make_update.sh pfSense.img pfSense-update.img IMGFILE="$1" IMGUPDATE="$2" echo "Image file: $IMGFILE" MD=`mdconfig -a -t vnode -f $IMGFILE` echo "Image file device: $MD" dd if=/dev/${MD}s1 of=$IMGUPDATE bs=64k gzip $IMGUPDATE echo "Update file created: ${IMGUPDATE}.gz" mdconfig -d -u ${MD} Additional information about some of the steps used in these scripts is on the documentation site at http://doc.pfsense.org/index.php/Modifying_Embedded

Hi, welcome.  :) The CPUs that are directly supported by the est(4) driver (and hence powerd for Speedstep) are the 400MHz FSB Pentium-M. The Dothan core uses less power and has more on board cache: http://en.wikipedia.org/wiki/List_of_Intel_Pentium_M_microprocessors#.22Dothan.22_.2890_nm.29 The 735 and 745 can be had cheaply and the 725 and 715 are extremely cheap! All are faster and cooler than the Celeron. Here's what I've actually tried: http://forum.pfsense.org/index.php/topic,20095.msg177606.html#msg177606 Steve

wrong seting ..after look around in the internet i managed to get it right. Thanks ..

Perhaps the device that can't do anything doesn't have a route to direct traffic over the tunnel.

Whew! That's what I was hoping for! Thanks to both you guys for the quick replies. Greg

@stantor: I may have found a solution to this. I installed EasyBCD on an windows XP machine. I configured EasyBCD to use an ISO pointed to a location on the hard disk, saved the settings and rebooted. On reboot I got a boot option to go to windows XP or PFSense. On selecting PFSense I was able to load the ISO file and go the menu options to install PFSense. Did it fully install?  Because, if I remember correctly, EasyBCD just alters the boot loader / ini, which pfSense should also try to do on install, either before or after it creates partitions, probably erasing the ISO in the process since it's on the drive it's installing to.  If it even got that far before declaring failure (assuming it detects that it can't mess with a partition that it's in use.) But, let us know if it works.

It also happens if you have a domain names defined in a hosts file, or even on the firewall itself.  Go to System -> Advanced and check "Disable HTTP_REFERER enforcement check" and depending on your environment you may want to check "Disable DNS Rebinding Checks" as well.

podilarius, you hit the nail on the head. I when to "Updater Settings" and set "Default Auto Update URLs" to "pfsense amd64 stable updates", clicked the "Save" button (which set the "Base URL" to "http://updates.pfsense.org/_updaters/amd64"), and everything is GOLDEN! Thanks again!

Thanks for the heads up Steve. My wan is about 20mb/s (download speed) I will do the install tonight on a dual core 2.6ghz system,  it uses just 50watts of power when running, the old P4 box is sucking about 130w!!

Solved, another IT guy had created a new machine on the vmware using the same IP, without checking or updating our static-ip document  :(

pfSense is a customised version of FreeBSD. It is distributed as a complete OS. Do not install FreeBSD, everything you need is on the pfSense CD (or memstick or Nano image). Steve

Hi Steve That's sorted it :) Many thanks for your help and to the other contributors. Best Dude