Yes it's call Internal Netvork NIC 1:           MAC: 08002709B490, Attachment: Bridged Interface 'Intel(R) PRO/1000 PT Desktop Adapter - VLAN : VLAN77', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: de NIC 2:           MAC: 080027FFC74E, Attachment: Bridged Interface 'Intel(R) PRO/1000 PT Desktop Adapter - VLAN : VLAN33', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: de NIC 3:           MAC: 080027744D96, Attachment: Internal Network 'intnet', Cable connected: on, Trace: off (file: none), Type: 82545EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny NIC 4:           MAC: 08002735E8F6, Attachment: Bridged Interface 'Intel(R) PRO/1000 PT Desktop Adapter - VLAN : VLAN44', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: de NIC 5:           MAC: 080027F3FAE9, Attachment: Bridged Interface 'Intel(R) PRO/1000 PT Desktop Adapter - VLAN : VLAN99', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: de NIC 6:           MAC: 08002796CC45, Attachment: Bridged Interface 'Intel(R) PRO/1000 PT Desktop Adapter - VLAN : VLAN66', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: de NIC 7:           disabled NIC 8:           disabled One thing to remember is that nic's in virtualbox needs to be intel nic's else it won't work in pfSense [image: nics.jpg] [image: nics.jpg_thumb]

I can verify you can do this in XenServer 6.0. It's not a paid feature. You create a new V-app and assign vm's to the v-app. Once this is complete you can then assign a start up order, delay, and priority with any vm. No need to modify an config files like cougarmaster has linked. XenServer 6 takes care of this for you.

@tommyboy180: When it's stable. BETA software is fun, but not always the best decision. I lost all my guest systems once because I wasn't careful. It's released

VMware Workstation 8.0 did the trick. The problem is gone now :-) Additionally I have to say that i've rebooted the Host Machine with a custom compiled Kernel (Debian Squeeze).

See also in this topic http://forum.pfsense.org/index.php/topic,39331.0.html I am having the same error. And the only conclusion i came into was that AMD cpus is causing that trouble.

Oops. too much work and not enough sleep.. totally forgot i had already written this.. sorry.

Not sure that's even possible. Most VPS providers handle the OS deployment side and only allow you to redeploy or possibly change to other supported configs. I've never seen pfsense as a supported config. If you can get FreeBSD on there you could load pf but it won't be pfsense exactly. Plus not all VPS providers give you an actual virtual instance, some are one OS with sandboxed partitions creating the virtual instance. What is your goal here?

Check out Mastering Vmware Vsphere by Scott Lowe

@Pootle: @abiscula: Regarding pass through, have you used any unsupported card? Have you ever tested it with a fast ethernet card? Not sure what you mean by fast - I'm using a couple of realtek gigabit cards passed through, it's not easy to find a pci-x NIC that isn't supported in ubuntu… I'm really interested in this setup but before replacing my processor with a vt-d one I need to make sure fast ethernet old PCI cards are supported by VmDirectPath (Pass through) Given the IO is passed through, I don't think that the card is particularly relevant.  I'm running with pci-x cards.  You could potentially use pci cards, but the pass through capability will pass through all the pci cards (or none of them). I've never tried pci pass through - only pci-x. Remember that the motherboard has to be IOMMU capable as well… Working with an intel DP67BA just need to get a new processors since I did not know core i3s do not support VT-D.

Sorry then i misread someparts, (almost half of your post) There have been some updates, when something small is broke for a day or so. after upgrade everything works well

Alternately, from the console shell, run: pfSsh.php playback enableallowallwan And then get in from the WAN side. Before you do anything else, setup a proper WAN rule to let you and only you into the GUI from WAN, and then remove the allow all rule that the above command added.

Are you running pfSense in a VM - if so which one? Can you post a screenshot of the LAN rules? What packages do you have installed?

Oh, sure.  Hot snaps.  I've done that too (when upgrading my ubuntu server).  I don't bother in the pfsense case, since the firmware upgrade requires a reboot anyway, and a hot snap is a lot slower (at least given that I have 1GB RAM that it needs to snapshot), versus the cold snap which is 1-2 seconds tops.

So nobody has tried to use Virtual network adapters for PFSense? edit Figured it out. First, set the host adapter to manual IP of 172.16.0.1, Subnet of 255.255.255.0, gateway of 0.0.0.0. Use VMnet2, not 10 or higher. I'm not sure which of these changes made things work, but it does work.

To get sticked I think there is some work to be done by other member. I fell alone with this topic so I give up for the moment (other things to do like my wedding for example). I think the best way is to use the appliance part of pfSense build tools, we also need a lot of patches from last kernel and xen devices (the xn network device for example that need some improvement if we need to manage VLAN inside pfSense or QOS with bandwidth tweaks). Feel free to try and Improve the receipe, if this topic is moving on, I will do my best to continue my work.

@ciela2: Everyone should be aware that the VMware Player installation is often missing a critical file called vmnetcfg.exe. If you don't have this file, advice about configuring your virtual interfaces won't even make sense to you–it didn't to me anyway. I found instructions for retrieving this file at the following web site: http://superuser.com/questions/187767/why-vmware-player-3-1-1-missing-the-vmnetcfg-exe-utility-and-where-to-get-it Thanks so much for saving me much frustration.