Well, the DNS blacklist can't work if it's not being used.  You need to configure the clients to use the pfSense server as their DNS server.

Yep you are right.  I just add two nics (do not pass through.) [image: pfSense_VMWare.png] [image: pfSense_VMWare.png_thumb] [image: Nic.png] [image: Nic.png_thumb]

Thanks!

Run /etc/rc.conf_mount_rw before you try to alter anything, and then /etc/rc.conf_mount_ro afterward. This will change the filesystem to read/write, and then back to read only. The GUI package system does this internally. The filesystem for NanoBSD runs read only all the time to prevent writes to the CF which could cause it to wear out.

Thats is bang on!  My sincere gratitude!  You dont know how much stress you have saved me! It works like a dream now! Thank you!!!

It's more of an issue with the iLO actually resetting during the OS bootup.  Go to HP's website and get a new BIOS to fix the problem. Specifically, you're looking for: Systems ROMPaq Firmware Upgrade for HP ProLiant ML310 G5/DL320 G5p Servers

@wallabybob: Have the looked at the installation screenshots at http://forum.pfsense.org/index.php/topic,7356.0.html? You can find links to quite a bit of documentation (including a link to the above screen shots) by following the documentation link from the pfSense home page: http://www.pfsense.org My recollection (its quite a few months since I last did an installation) is that you boot from the live CD, configure, then select menu item 99 (Install to hard drive) then when done, remove CD and reboot and then, if the installation went well, you will be running off the hard drive. The CD is designed so that you can try  pfSense running off the CD before writing anything to the hard drive. Thank you, that explanation helped alot…

I need to use only the squid and squidguard application for local proxy server so I only need one nic

There's a virtualisation forum with many posts in it that you should read. Key points: Virtualisation will always add a performance overhead - however you shouldn't notice it unless you'd be running the physical hardware at near 100%. Virtualisation introduces security risks since as well as vulnerabilities in the (now virtualised) host you now have vulnerabilities in the virtualisation platform.

@wallabybob: Unfortunately some manufacturers use the same model name for products with different chipsets. It looks like your card might be an example. Since FreeBSD claims to support your card its worth submitting a problem report to see what happens. Ok, thanks. I submitted bug #101.

@0tt0: This also covers my question then, about 1.2.2 -> 1.2.3RC1? Should upgrade via console followed by re-install of all packages be sufficient then? That should work. You can upgrade however you like: console or WebGUI. Reinstall packages after and you should be fine. As always, keep plenty of config backups and some install media handy just in case, but I haven't had one test (or live system) go wrong when upgrading along any part of the 1.2.x branch.

Packages are installed from the Internet, they are not included in the CD image. Click on System -> Packages then click on the "+" to the right of the package description to install the package.

I burned off the lastest snapshot and it has the option to install it via a installer rather than the 99 option. The installer worked and problem is solved!

@mathias: But even though the baud rate isn't set properly you should see some sort of output. Not always.