I have one ethernet adapter on my motherboard.

Kinda late I know…but if you are using ESX...you just use VGT to allow VLAN Tagging through to the guest OS (pfSense). To do this, you setup a Virtual Switch with a VLAN ID number of 4095 - this means that all VLAN info will bypass the standard VMware and be passed right through to the guest.

I use this instead of Virtual IPs because these IPs are pingable (the Virtual IP ones are not because of the way that ESX handles the CARP stuff from pfsense)

I am doing this here with great success.

Also, I would recommend changing your NIC to use the e1000 adapter instead of the standard one.

Jim

Do Not use VMware 6.5, v6.0 working fine…..

That was the reason why I assumed, that CARP interfaces could take settings from physical ones. To be more correct - vmnics (but in this post I would chose to name them physical - NICs, which are assigned to VM during VM setup from console, but not physical NICs on server hardware). My vmx file does contain only records assigned to these "physical" nics.

ethernet0.virtualDev = "e1000"
..
..
ethernet3.virtualDev = "e1000"

CARP interfaces are created in VM using web GUI configuration. Should I manually add these drivers to vmx file? How about limitations on VM to have maximum 4 vmnics?

I never used vi, where can I loacate a how to use it.  Just curious?
RC

;D  I now am running on XEN 5.0.0.  Here is the hardware that I am running on.

AMD Quad Phenom 2.5 processor
MSN-SLI motherboard
6 GB of ram
512 mb SLI video adapter
Broadcom 1 GB adapter
On board ethernet adapter
dual 100 mb Intel ethernet adapter
3 x 320 GB HD's (non raid array currently)
550 watt  power supply

Replacing the following servers:
DELL SC1500
DELL SC 440
COMPAQ DL360
COMPAQ DL380

It's a mix of production and test boxes.  For hosting servers and devices that you will access it's great.  It's working awesome.
RC

Great that it works now, but have you seen my comment on VirtualSMP in Vmware?

You should not use this with something like a firewall where SMP doesn’t bring huge performance improvements anyways(and timing is important).
Not only will it perform much worse, it will slow down you’re entire host.

With 1.2 release I get only 64MBs recognized out of 512MBs that I have configured in virtualbox. With one of the 1.2.1 snapshots I have tried I get full 512MBs recognized.

Someone interested in doing a little research digging should look into using the free vm tools that FreeBSD has under
ports/emulators/open-vm-tools. these are the open source versions of the VMWare tools binary blobs.
http://open-vm-tools.sourceforge.net/about.php

this might actually lead closer to just having a VMWare support package as it will be just another port added to the list to precompile.

Falcon4 - while you're entitled to your opinion, you might want to try to avoid coming across like a troll ;)

FreeBSD has a massively smaller developer base than Linux, and companies like VMWare put less effort into supporting it.  As with any open source project, only the things the developers care about have work put into it.  With few developers the rate of change can't be the same as with Linux.  The support it gets from commercial vendors tends to be focused on the server space (Intel, 3Ware and others produce and support drivers for their products).

That said, if you enable the e1000 network driver instead of the default then you can use the em driver for FreeBSD, which is supported by ALTQ.

I had the same problem with my network. my two routers is connected to the backbone and to the pfsense. i was having duplicate name errors. i made 3 rules blocking 3 kinds of netbios on LAN, WAN1 and WAN2.

i put he load balance rule below the 3 (netbios block) rules in the LAN. so far i have'nt found any problems..

please post any problem you might think i encounter by doing this settings.

I am having this exact same issue. However, I made the changes that you made, and it still doesn't work. The thing is, I removed one of the NIC's. So the machine NIC and PFSense's LAN NIC are the same physical NIC. (I needed a NIC in one of my other machines).

I'm thinking that is the problem, but I was wondering if anyone has any ideas. Or do you know on a more technical level, as to why that fixed it?

Not sure if anyone is paying attention to this thread, but I just found something new. It looks like I only experience this problem when I connect to the RDP console session(using mstsc /console). If I start the terminal services client without the /console switch, it works just fine.

I still can't figure out why that is the case.

@karsteb:

Linux kernel based virtualization (kvm) was introduced into the kernel in linux version 2.6.20.

So now, linux have full virtualization (but no paravirtualization) built into the kernel. Anyone tried to get pfsense running under it?

It seems that XEN has problems under Intel hw, and wmare ESX is costly, but according to this page http://kvm.qumranet.com/kvmwiki/Guest_Support_Status kvm seems to support BSD's just fine…

k

Interesting.  Give it a shot and report back!!

Nice card, didn't know they made anything like this.
In my case though the onboard gigabit NIC is probably much better than this 5$ card, but for lower end server I always take cheap Realtek cards.
Thanks for the link.