In my Hyper-V setup I set a vNIC for each VLAN.

IE, I have a vNIC for LAN(3 port LAGG), WAN(separate port) that are using default VLANs. Then 2 more vNICs with the VLANs tagged in the adapter settings(using the 3 port LAGG). So as far as pfsense is concerned each 'VLAN' is actually a separate physical interface.

This is probably not an ideal setup for more than a couple VLANs given there is a max network adapter you can have, and it would be pretty messy even if you could, but it works quite well for my purposes.

I know this is an old post,but as long as you choose "other install media" template when installing, it's automatically PVHVM

an easy way to check it's using PV drivers in an HVM VM is go to status>interfaces, they should be named xn0, xn1, etc

Your actually quite behind for build numbers, the current build is 4510822, which is 3 newer than what your running.

I have been running pfsense on esxi for many years and have never seen such an issue.  But then again your issue has ZERO to do be it the pfsense was virtual or on hardware.

You should create your thread in different area, maybe the general area..  What your seeing has zero to do with system being vm or not.

Yes, I believe this should work, I have used several versions of pfsense running on multiple vlans in this way.

You are basically trunking all vlans to the port group and allowing pfsense to do the the tagging instead of the virtual switch or port group.

Ok Problem was fixed. It was port issue. Only 2 connections were allowed.

Personally, I ran pfSense on KVM, with openvswitch.

It worked like a charm, truth be told. Plus, with virtIO drivers, the uplinks to the virtual pfSense were 10Gig. And using openvswitch, the .1Q part was done entire outside of pfsense on the virtual switch.

The pastebin pages were removed so I can't see what it said. I run over a dozen VMs in ESX and none ever crash, and I know customers using it in production with no issues as well.

It could be a hardware issue, a driver issue or OS issue triggered by some combination of options in use. Hard to say, but it isn't a widespread issue.

Apologies I thought I had replied to this thread to thank you. I just wanted to confirm this was the issue for anyone else who might find this thread via searching in the future.

Been running pfsense on esxi for years.. Hundreds if not 1000 is not 10's of thousands of people run routers/firewalls on VM.. Yes it a standard practice..

Care to document a screen shot of your Virtual Network Editor?

I do this with 2 bridged adapters. One for WAN (VMnet0) and one for LAN (VMnet2).

I changed the vm settings and it seems to be all good now.  :)
After reading the hardware requirements https://www.pfsense.org/hardware/:

501+ Mbps -> Multiple cores at > 2.0GHz are required. Server class hardware with PCI-e network adapters.

I ended up with more cores…

@johnpoz:

What are you hiding here, is that your pfsense setup?  Why would its lan/wan be the same vswitch?

Well, yes… I am hiding the public dns/ip.
Arguably lan/wan on one vswitch doesn't make much sense and I will change that....

What are those other networks on each vswitch.  I don't see more than 1 vm on those switches - so only pfsense?

So what is your Iperf THRU pfsense.. ie that is routing/firewalling..  Testing to pfsense IP is not a valid test of the performance of pfsense as a router/firewall its a test of how fast you could move a file to pfsense directly, etc.

I did a lot of file transfers and watched the traffic graph max out around 950 or something… I will do iperf through the pfsense as you recommend and report back tomorrow.

However I can mark the thread [SOLVED].

Thanks

Use fixed size virtual disk, not dynamic.

offloading IN the virtual machine (esp. RX/TXSUM), you probably should have it disabled all offloading ON the host - sometimes you need to disable it too (but check VM first)

Its work fine

PFsense can access the internet , but loses the connection after 10-20 sec and its not coming back :-(

And i can´t ping my server from my home pc

A quick followup on this issue:

This issue is not related to the virtualisation, it is related to negative drift coefficients. My hardware requires a drift coefficient of approx -15.

The drift file /var/db/ntp.drift is either being removed (due to a negative coefficient?) or is not saved across a system restart. I am not sure which is the case. At this stage I have not had the time to investigate. All I know is that when I log in after a pfsense restart there is no ntp.drift file.

In this situation NTP starts for some reason with +500 as the drift. Given that the hardware requires -15 it takes a very long time for the NTP daemon to sort things out. In my case I can fix the problem instantly by:

1. Stop the NTP service from the pfsense web admin.
2. Create the /var/db/ntp.drift file and put in -15.000 as the value
3. restart NTP from the web admin

If I do this the entire NTP system stabilises in no time (5 minutes) and everything is OK from then on.

Tim

It does help to reboot once the new tools are there indeed :p Then VMW and BSD both know about their capabilities and it actually works ;-)