Hi RC,

Thanks for the bump, I forgot that I posted this. What I ended up doing was trying the exact same installation on Xen 5.6, and it worked the way I expected it to.  (ie. Able to have multiple interfaces and ping out, etc.)

I suspect there was something wrong with the virtual interface or interface drivers when running on Xen 5.5.

Since I've got it working, I don't think any further troubleshooting is necessary.  Thanks for the response :)

ang -

even without the link state information, pfsense still performs without too many issues

Setup untangle in transparent mode when your doing the install.
Example of the switch setup:

vswitch0 - WAN
WAN <-> pfSense WAN

vswitch1 - Internal Router
pfSense LAN <-> untangle WAN (In transpartent mode, you give it a static IP for your LAN)

vswitch2 - LAN
untangle internal (LAN)  (No IP since its bridge to the WAN interface)

Accept promiscuous mode needs to be allowed on the interfaces with untangle. I believe both need it but its been away.

I've tried this setup on EXSi and it was really slow when untangle was put into the mix but i was running this on an Atom d510.. Been meaning to try this on a XenServer to see if it improves..

Thanks for the info.  Even though it showed the kernel was smp, it did not show 2 processors.  I ran the commands anyways to switch it, and on the next reboot it showed smp again, but this time both processors were shown.  So 1.2.3 worked in vm.
  As I now have a good vm setup, I eventually got 2.0 working and settled on 2.0.  Seems to work better, and it is the future.
Part of the vm idea to me is also the ease of use of it.  take snapshot, then try upgrades.  If all dies, revert to a saved image.  My windows boxes has always been this way, but switching the router over was a bit of a conceptual change for me.    Physical boxes only good for NAS setups/vm boxes for me from now on.

Thanks again for the tips.  It's appreciated when the developers have time to help us out!

Of course, if you want to manage this beast you will have to virtualize yourself (or access from the WAN).

you've watched too much Tron and/or Matrix movies ;)

@ultranet:

Hi,

I installed pfsense for the first time today and ran into a problem, after it was connected I couldn't get a connection to the web. I could get msn/skype etc but I just couldn't browse any web pages.

The pfsense appliance also couln't do a ping to say google or download/check for updates.

What I have on the network as follows:

DGN3500 Router (modem only mode) (asdl) plugged into phone line> VMware Server Plugged into DGN3500> pfsense applicance installed on VMWare Server

le0 = set to my ISP static IP (Using their gateway etc)
le1 = set as my lan (192.168.x.x)

Anyone forsee an issue with this setup or where I am going wrong?

Thanks
Sam

have you set your pc's ip static?
if for example your lan ip is 192.168.1.1
then you need to put this in your tcp/ip of your host pc
ip: 192.1068.1.2
subnet: 255.255.255.0
gateway: 192.168.1.1
preferred dns: 192.168.1.1

create a seperate Vswitch for "pfsense wan" and "pfsense lan" and assign a physical nic to each.

the third nic will be the vm management network switch for your LAN and other vm's.

@adrianp918:

i did this and all works great!!!!

now one issue i do see and i dont know if it is a bug or what but it is as follows

when i set my modem to do the ppppoe and have my pfsense box get a ip addy assigned to it, it works great

when i tell my modem that i will be using the pfsense box to do the pppoe and then select pppoe from the dropdown menu on the pfsense box and fill in the user login information

it tells me to apply the setting
i then hit apply

and then when i go to the dashboard it has a big red X on the wan interface and says it is disabled and then i go to the interface section and i hit connect it doesnt connect, but when in dhcp mode it works flawlessly

any idea what would cause this?

nice to hear that..^^

by default the lan ip of PFSENSE goes to 192.168.1.1

i would try that

this is excatly what worked for me

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

and he was spot on with everything, just make sure under your vm settings when you are installing your product on the host computer, that you select the vmnet interface after you have the initial one that is automatically created for you via the vm interface

meaning once you go thru your setup
go back and add 1 or 2 or how ever many nics you have and have them set to your vmnet that you applied in the host server virtual networking section

that is where i was confused but once i slowed down and re read all the directions over and over it was like DUHHHH

then boom it all worked like clock work

Right, because they aren't the tools it knows about, and they would break things if you updated them that way. That's why the package exists. :-)

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