@cmb:

I was seeing this on 1.2.1 also, but thought it was something weird going on with my system as it worked on other systems and nobody else has reported any issues after a few thousand downloads.

The 1.2.2 VM is available now and it doesn't do that for me at least.

That solved it!!  I spend close to a week trying to understand what was going on, it worked first try with 1.2.2

Thanks

I had the same problem and solved it by switching to Intel Pro/1000 T-Server network adapters.

Apparently it's a bug in FreeBSD, see http://eligere.wordpress.com/2008/03/05/virtualbox-156-freebsd-70-and-pcnet-fast-iii-problem/

Unfortunately, I figured it out after messing around for quite some time.
Perhaps a notice should be added to the download page, since it's pretty common to try it under a VM.

Edit: I'm using VirtualBox 2.0.6

If you want to keep the firewall rule functionality so you can filter packets, you can just disable NAT by going to NAT, Outbound, change it to manual and delete the rule. This will allow it to function strictly as a router with the ability to filter packets.

@Cry:

If the adapter is supported by FreeBSD then yes it's possible.  However, if you connect to a USB 1 port you'll be limited at a maximum of 12 Mb/s.  VMWare probably has some overhead too, so whatever theoretical bandwidth you're expecting, you'll probably get less.

Just trying to see whether it works. What do u mean by "supported by FreeBSD then yes it's possible." I want this USB doggle to act like my wireless AP. Or can i hook up my trusty wrt54g to do the job? which is better?

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.