I'm now having trouble with pretty much every virtual software - on Xen I can't even figure out how to make it happen (on OpenXenManager) and on XenServer I only have a trial so that's out.

On VMware ESXi 5.0 Enterprise Plus I can see the HW pass thru in the configuration but every time I've selected it the system freezes during boot and I've had to re-image the system.

This is a Dell dual-xeon motherboard, not in a server chassis but its a Dell Precision T7400 Workstation - the same exact chipsets that are included in all Dell servers of that vintage.

I have two items in my BIOS related to Virtualization - VMM and Intel VT for Direct I/O. Both are turned ON.

I'm at a bit of a loss because the ESXi 5.0 is a legit licensed (non-trial), fully paid for, etc. VMware support wasn't much help. Its frustrating to be able to see it but not utilize passthru.

Also - The VMware ESXi uses a driver that pfSense recognizes so my only issues with passthu are really the Cisco AIR-PI21AG-A-K9 wireless card (to the pfsense or even having ESXi recognize it) and video cards (not related).

I should have the ability to allocate and share GPU on this version (enterprise plus) as well as pass thru the Cisco AIR-PI21AG-A-K9 card directly to pfSense, which I can't.

Thx for any help, thoughts, suggestions, etc.

@jimp:

By default, pfsense blocks access on the WAN.

True when you have more than one interface, when you have only one interface there is the anti-lockout rule that should solve the problem above  ;)

The most common problem that I have rasd about, is the nic speed in HyperV. Even though I will not use pfsense for routing networks, just Internet traffic (WANs), I ave read that the bigger speed that legacy adapters used on HyperV is 22mb/s.

Kostas

That interesting … I have had to do that on every ESXi deployment I have done.

Can anyone who knows XenServer help me with installing the XenServer tools to pfSense? Is this possible?

All of my NICs are showing up as 100baseTX <full-duplex>.

This was the case on the windows installs as well until I installed the XenServer Tools.

It has a Windows and a Linux option but nothing else.

Looking for the proper drivers for these Citrix/Xen virtual interfaces.

Thx.</full-duplex>

I know this is an old thread, but in case anyone else is looking for information on the topic I will add what I have experienced.

I ran pfSense in a VirtualBox VM for a couple of years with no problems and then it quit working.  What I discovered recently was that two problems coincided.  First, I had set up the host using bridging from bridg-utils and then used bridged adapters from the guest.  This was overly complicated and I confess that I never fully understood the configuration that worked.

The second problem was that my ISP changed (quietly without notice) to limit my connection to only one IP at a time and set that IP on a different subnet than the DHCP server.  This caused the host to grab the IP address on boot and then pfSense in the guest could not get one.

I believe globexgr is correct in the recommended configuration.  That would be to set the host to grab the IP from the ISP and then do a "host-only" connection from the guest VM red interface to that host net.

Then I would do a bridged output from the Guest to a static IP on the host Green interface.  Alternately the host "green" adapter could be set with another IP net address and the guest could host-only into that net.

All in all the best advice I have seen is Draw The Network Diagram including the virtual parts.  That is what I intend to do before I dive back into the current firewall and see if the new setup solves both problems above.

One caution to all this, however, it is my understanding that if you use a pure bridged connection from Guest to Host then you bypass the Host TCP Stack.  If your VM is a firewall that would be safer than using host-only.  But everything I have read says that I am not able to do that because a bridged VM adapter cannot work on a "single IP" type connection like my ISP implemented :-(

Hope this is useful to someone.

@jimp:

Add the key to the admin user in the GUI. The admin user in the GUI is the root user (and admin…) in the shell. The key from the admin user in the GUI is written out at boot time, which is why your manual edits are being wiped out.

Ah! Thanks for this tip… the mystery has been solved!

FWIW I've since moved from using pf in a VM to a dedicated thin client box.  Greatly improved situation since now I don't lose internet simply because I need to bounce the server.  Was nice for testing though.

Thank you all for the help - it was exactly what I needed.
My Vm is now running 2 vcpu's and everything looks as it should.

Connect the WAN port to the modem/router and the LAN port to the switch.

Ill try that immediately in the morning..

and see what happend. Im out for this momment

Thanks pfsense and sir cry havok for all the troubleshooting help

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

nics.jpg
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).