try this bro OS: windows xp 32bit vmware workstation pfsense 2.0 rc1 go to network area connection of your host pc and set this: onboard nic (LAN) - uncheck vmware bridged protocol only in properties the rest check nic1 (WAN) - check vmware bridged protocol only in properties diagram: modem/ISP >>>>> WAN (nic1)    pfsense in vmware workstation …..................... (LAN) onboard nic >>>>>>>> switch/hub virtual network editor in vmware workstation setup before going to pfsense installation vmnet0 - bridged - select your onboard nic vmnet 2 - bridged - select your nic1 note: remain vmnet1 & vmnet8 as default settings vmware adapters network adapter - custom - vmnet0 (bridged) network adapter2 - custom - vmnet2 (bridged) then you can now proceed to installation after installation, default lan ip of pfsense will be 192.168.1.1 you can change that according to your likeness go back to your network area connection set your lan nic(which is your onboard nic as what i use above) go to tcp/ip and apply this ip: 192.168.1.2 subnet: 255.255.255.0 gateway: 192.168.1.1 <<<<<< must be same with your lan ip of pfsense preferred DNS: 192.168.1.1 put this in your browser 192.168.1.1 username: admin password: pfsense that's it! hope it helps

here is an init-script I found ad vbox-forums some time ago. as its no longer adjusted to new versions von vbox I modified it on my own working fine with vbox 4.0.8 on ubuntu I dunno anything about mandriva but i guess on principle it will work - maybe you will need to do some little changes #! /bin/sh ### BEGIN INIT INFO # Provides: virtualbox_vms # Required-Start:    $local_fs $syslog # Required-Stop:     $local_fs $syslog # Default-Start:     2 3 4 5 # Default-Stop:      0 1 6 # Short-Description: Control VirtualBox Virtual Machine instances ### END INIT INFO # # Original Version 2008051100 by Jochem Kossen <jochem.kossen@gmail.com> # http://farfewertoes.com # # Released in the public domain # # This file came with a README file containing the instructions on how # to use this script. # # Modified my Plexus # . /lib/lsb/init-functions # Are we running from init? run_by_init() {    ([ "$previous" ] && [ "$runlevel" ]) || [ "$runlevel" = S ] } ################################################################################ # INITIAL CONFIGURATION VBOXDIR="" # path to the file "machines_enabled" including the list of vbox-machine names VM_USER="" # user starting the vbox-machines ################################################################################ # CHECK CONFIG export PATH="${PATH:+$PATH:}/bin:/usr/bin:/usr/sbin:/sbin" if [ ! -f $VBOXDIR/machines_enabled ]; then    echo "ERROR: $VBOXDIR/machines_enabled does not exist. Exiting."    exit 1 fi SU="su $VM_USER -c" VBOXMANAGE="VBoxManage -nologo" ################################################################################ # FUNCTIONS # Check for running machines every few seconds; return when all machines are # down wait_for_closing_machines() {    if [ `$SU "$VBOXMANAGE list runningvms" | wc -l` != 0 ]; then        sleep 2 echo -n "."        wait_for_closing_machines    fi } ################################################################################ # RUN case "$1" in    start) cat /etc/virtualbox/machines_enabled | while read VM; do if [ `$SU "$VBOXMANAGE list runningvms" | grep Test | wc -l` != 0 ]; then log_action_msg "Virtual machine $VM already running..." else log_action_msg "Starting VM: $VM ..." #$SU "$VBOXMANAGE startvm $VM --type headless" $SU "screen -m -d -S $VM VBoxHeadless --startvm $VM --vrde=off" fi done ;;    stop)        # NOTE: this stops all running VM's. Not just the ones listed in the config        $SU "$VBOXMANAGE list runningvms" | awk '{ print $1; }' | sed -e 's/"//g' | while read VM; do log_action_msg "Shutting down VM: $VM" echo -n "\tWaiting for closing down VM..." $SU "$VBOXMANAGE controlvm $VM acpipowerbutton"        done        wait_for_closing_machines echo        ;;    start-vm)        log_action_msg "Starting VM: $2 ..."        $SU "$VBOXMANAGE startvm \"$2\" --type headless"        ;;    stop-vm)        log_action_msg "Stopping VM: $2 ..."        $SU "$VBOXMANAGE controlvm \"$2\" acpipowerbutton"        ;;    poweroff-vm)        log_action_msg "Powering off VM: $2 ..."        $SU "$VBOXMANAGE controlvm \"$2\" poweroff"        ;;    status) if [ `$SU "$VBOXMANAGE list runningvms" | wc -l` = 0 ]; then log_action_msg "Currently there are no virtual machines running..." else log_action_msg "The following virtual machines are currently running:" $SU "$VBOXMANAGE list runningvms" | sed -ne 's/[^\"]*\"\([^\"]*\)\"[^\"]*/\1 /p' | while read VM; do echo "\t$VM (`$SU "VBoxManage showvminfo $VM" | grep "Hardware UUID:" | sed -e "s/^Name:\s*//g"`)" done fi        ;;    *)        log_failure_msg "Usage: $0 {start|stop|status|start-vm|stop-vm|poweroff-vm}"        exit 3 ;; esac exit 0</jochem.kossen@gmail.com> of course I will have an sympathetic ear if anyone being well familiar with bash flying over this script has any suggestions to improve…

After trying a lot, I have to use VNC instead of RDP.. It's much simpler to use VNC and there is no problem. :)

have you added the additional hardware under the settings?

After setting the virtual HD to 20GB, it's working (at least installing right now) in Hyper-V.  It failed saying it couldn't find the hard drive either IDE or SCSI saying it was the wrong number of cylinders.

Try all of the options under point 4 here: http://doc.pfsense.org/index.php/CARP_Configuration_Troubleshooting

Hi Patrik I think it's working as it should be, the WAN card is suppose to be connected to the Internet, he it shouldn't get any DHCP addresses..  The 4-port card would be waiting for an external modem of some type. Have you tried to configure the modem or modems? Thanks Y.

@georgyous: Hello, I am reather new to freebsd, the first freebsd based machine that I worked with was pfsense. This could be a stupid questions, but I need an answer. How could I get a download link for the curent kernel sources in the 2.0 snapshots. I've worked with linux, in linux it is simple to download the kernel sources ex(gentoo): emerge kernel sources , does freebsd support something like this? I am trying to compile the curent kernel with xen support, becouse from kernel 2.6.32(I think) avery newer kernel(from kernel.org) has xen support buildin. I've seen a thread on citrix forum, with people that managed to get a working freebsd 8.0 macheen with pv kernel. Why not do a Pfsense xen virtual appliance? Thank you! Have you succeed in any manner ?

Up, I try to make my own without succes.

I have now reinstalled using the cnet network cards with virtualbox, I have tried using the intel's with no luck. Then I boot up and find that I can ping out to 192.168.1.1 but i cant ping any of my other network interfaces on the network which is also on the .1 range. I am really lost, I cant even ping my host mandriva box from PFsens virtual machine not to mention access the web interface of pfsense. PLEASE Help, I am as you can see desperate for answers ….

Your host's driver is still involved, since it has to for Virtualbox to use the interface. Then Virtualbox is involved and finally the guest (pfSense in this case). If somebody finds an exploit in either the host or Virtualbox that can be exploited remotely then they can bypass pfSense. It's all about risk management - you have to decide if the risk is worth the benefits. Is the extra complexity over just running IP Tables worth the features that pfSense brings, and the increase in risk?

Looks like it is working. I ended up changing the subnet to 10.0.0.x instead of 192.168.20.x. Thanks for the help.

after the initial install using a web browser on the local network  connect to pfsense to finish the install. the default i/p is 192.168.1.1  ,  login  : admin,  password : pfsense. also  from the proxmox gui, open a vnc console to check the local i/p address, enable ssh etc..

This is not a VmWare support forum…. ;) Sorry. Pfsense related issues only.

I am also looking into something similar in order to make my rack at home more green. You'll need a managed switch and a dedicated NIC in the host box.  VLAN your WAN to the dedicated NIC. And yeah, security could be an issue.  Do ur homework :)