Got it fixed. Had to make: loader.conf.local and add: hint.apic.0.disabled=1 On reboot, it works fine in normal mode. Safe mode disables a few more things like DMA, APCI, SMP, and hdd caching.

@cyclone3d: I also need to know if it is possible to: 1. Set IP according to MAC address In pfSense DHCP can assign a fixed IP address determined by the MAC address of the DHCP client. @cyclone3d: 2. (This one is kinda strange and hard to understand, but I will take a stab at it) - If a user has a specified IP by MAC address, and the user changes their IP, disable(block) that user. If a user is smart enough to change the IP address they are probably smart enough to change the MAC address. If you are worried about such users it would be better to put them on a separate interface (or interfaces) and use firewall rules to restrict access.

install the shellcmd package and set it up as a shellcmd, which gets executed during the boot process.

Are you sure that you don't have a keylogger on the system you are accessing the pfsense web GUI with? Could be that your system is compromised and somebody is changing your passwords without your knowledge.

Well, thanks for at least looking into it… :)

@asura: thanks i will give a try .. by the way ..i installed pfsense 2.0.1 on 500gb harddisk its stuck at boot screen. Screen only show me : F1 pfsense F6 PXE Boot: F1 \ mayb pfsense 2.1 will support my 500gb harddisk? thanks :) edit: with one shud i download? 1- pfSense-LiveCD-2.1-BETA0-i386-20120828-1442.iso.gz 2- pfSense-LiveCD-2.1-BETA0-i386-20120828-0823.iso.gz 3- pfSense-LiveCD-2.1-BETA0-i386-20120903-2218.iso.gz If you press ther F1 key on your keyboard, it should then continue to boot.

Thanks for that. That sounds like quite a handy feature, and good to know for the future.

It's been discussed many times here on the forum, list, etc. It's a security risk, and also unnecessary bloat. If you need more detail than that, search around on here and it'll turn up.

thanks!

after google around i found the answer http://www.hacom.net/faq/i-cant-install-pfsense-sata-drive

It's working! I wish I knew what it was that fixed it; I went to the WAN settings paged and it said there were changes waiting to be applied, I applied them and after that I noticed there was no gateway set.  I set the gateway and applied the changes and suddenly it works.  So it must have been something dumb I was doing, not applying changes or something, boy that was frustrating but I am so glad it works.  Thanks for your help with this guys!

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.