I've posted my, as yet incomplete, findings in this thread. Cheers.

Yes, you can. See the pfSense VMware Appliance. There's some more info in the Installing pfSense in VMware under Windows how-to.

HI Sam. Verify your address network, test if you can ping all hosts, but let me see if I understand you. You plug in router -> WAN pfsense You plug in Host -> Pfsense You plug in ? You´ve said that you have 3 real NIC, but you need to create 1 VSwitch on VMware ESXi and connect both Machines, if not you can until inside subnet network, but you can see both devices. FIRST ping all hosts see if you got sucess. SECOND verify your VSwitch created on VMware ESXi, if you want or can post it a screenshot of your VSwitch on VMware. But I was thinking that problem is here. Regards, Heitor Lessa

I've changed the NIC's to flexible instead of e1000, and now it doesn't report fragmentation problems, and I don't see any errors in transfers. Apparently there's a difference in the handling of large packets there.

I tried Ubuntu Karmic64 9.10 + virtualbox + pfsense 2.0 RC3..  I had no problems getting the host to talk to the guest(pfsense).. Also I was able to recieve and IP, from pfsense DHCP.  I believe I used one of the PCNET adaptors in bridge mode..  I could also log into the pfsense console from the karmic host. My only problem and I didn't have much of a chance to play around with it.. Was getting VLAN's to work.. I am doing this with only one NIC in the host. Here's my attempted setup: Pfsense Guest: LAN = ln0 WAN = ln0_vlan99 I have this connected to a Dlink switch that supports 802.1q. This setup worked right out of the box…

What version VMware that are you using? I had similar problem few days ago running under vmware, the problem began when I was adding a new nic, when I started … pfsense not works anymore. Resolution: Revert snapshot that i made when everything works fine. For your case... did you create any snapshot for you VM before this happens? Independent this, make a test, create a new VM under vmware and do a new install of pfsense and test the internet connection, if everything works fine, try to restore configuration in this pfsense box =). Any doubt, post again. Regards, Heitor Lessa

Perfect. Solved problem ^^.

Perfect answer, I´ll do the same.

I had some problemas too, but just with 1.2.3 version, now I´m using 1.2.2 w/ 200 users and works fine ! Try to change the version. And remember, take snapshot and backup too ever.

damn :(

WAN is connected to my router (192.168.1.) LAN is connected to a netbook I'm using for testing (192.168.2.) I've actually managed to get it working. I was using 3 NIC's, but when I disabled one and set WAN to VMnet0 and LAN to VMnet4 (For some reason, I can't assign the PCIE NIC to anything in the Virtual Network Editor) and pfSense is reporting a valid IP from the router and I'm able to access the gui from the netbook, but I can't route further with it. So I decided to test it going directly from the modem. And it failed to renew the IP. So I connected it back to the router, and it's once again assigning itself one of it's own LAN ips.

I am using Xen 3.2 and pfsense 1.2.3-rc3 for a couple of months and haven't faced these problems. It is running smoothly. Maybe you should try and reinstall or the nics if pci switch them around the slots.

Hi Rezin, Thank's for the Information now it works A short user manual how to use pfSense appliance with VMware Server 2.01 1.) Download VMappliance 2.) Unzip 3.) Edit the .vmx file and remove (comment) the lines     #ethernet0.virtualDev = "e1000"     #ethernet1.virtualDev = "e1000" 4.) Start the appliance 5.) Connect via VMware Remote Console and reconfigure the NIC's     le0 –> LAN     le1 --> WAN 5.) Set Lan IP 6.) Connect to the web GUI

install on your physically networkcard from laptop a second ip-adress with 192.169.1.2

Thank you for the reply Gob! I did forget to mention that im running Vmware Server ontop of a debian installation(ESX/ESXi doesnt support my hw:( ) but i guess i would go about it the same way. This isnt really related to Pfsense but does anyone know how to lock down an interface on a Vmware host running Debian ? People running Pfsense virtually should have some knowledge about this i guess ? Thank you!

To my knowledge there is no guide as until RTM R2 it wasn't even working properly. Its quite simple all you have to do is remove all the "Network Adapters" and replace them with "Legacy Network Adapters". These virtual  "Legacy Network Adapter" however don't seem to support vlans from within the vm so the trick here is to add as many network  interfaces as you need then assign individual vlans to them. I have been running 1.2.3 RC2 in a vm since 2k8 RTM R2 came out and all seemed fine but out of the blue one night the (until recently rock solid)  host rebooted! taking down all the vm's with it. This is of course really bad. I suspect it is probably freebsd playing up from within the vm or the legacy adapter not liking vlans rather than a Windows 2008 R2 bug. I am currently running R2 with the pfsense vm OFF to ensure server stability and then when I am sure again I will try to upgrade the 1.2.3 VM to v2 BETA and see if that is more stable. http://forum.pfsense.org/index.php/topic,12157.0.html [image: Untitled.png] [image: Untitled.png_thumb]

the frame check error had nothing to do with the fact that virtual machines behind the firewall couldn't connect to the internet. The vswitch connected to the public network needed to reconfigured to accept promiscious mode

Det pågældende netværk her er til en IT uddannelse, så man må gå ud fra at det også vil generere en del trafik af forskellig art. Ole Thomsen