When you bridge, only one interface gets an IP address in the same subnet. I had thought on 1.2.3 we had a little hack that let you put in "none" for the IP, haven't tried it in a while though. You can always put in an IP from another subnet, it doesn't matter, it shouldn't get used. So long as it's an IP in another subnet it should behave.

@Zeon: Hey guys, Just an update on this, after speaking with PFsense support they suggested I look at the dupelx settings on our switch where the WAN comes in. Sure enough the port was only auto-negotiating at half duplex. After setting this to forced 100mbps full-duplex and installing open-vm-tools everything is working a treat :) Thanks for feedback!

I am using VMware Player - not workstation, maybe that's why these answers don't make sense to me. Can someone explain the connection between pfSense IP addresses, VMware IP addresses, and Host Computer IP addresses? I'm sure I'm missing something obvious. Thanks

as i mentioned above, i use vmware workstation first. now i shifted to virtualbox coz it would not eat much on my host pc ram…^^ windows xp sp3 32bit virtualbox 4.0.8 pfsense 2.0 RC3 + lusca cache

Andy, Thanks very much for the detailed response. I've tried the chmod +x and it looks like it has worked. It still takes a while to boot pausing at "Configuring WAN interface" and at "Starting OpenNTP time client" but at least once it starts it works! Yes, I'm pretty sure that the underlying issue is that there is limited OS support in Hyper-V. I'm no expert in this but I think that MS is using a type of virtualization that works best when there is operating system support. I've not had problems with pfSense on ESXi or VirtualBox to name two competitors, but there are reasons beyond pfSense why Hyper-V makes best sense for me. Thanks again. Richard

I am a home user with a 15Mb down 1Mb up plan from my ISP, so unless I misread Mbits as Kbits my reply might not be too helpful.  However I have a near identical setup to yours, W2K8R2 with PFSense & Debian Web Host running in VMWare Server, I have experienced no slowdowns in internet speeds, and local speeds appear to be the same as before.

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. :-)