PfSense 2.3 on Hyper-V 2012 (R1) - only 3 network adapters are working
-
The FreeBSD patch linked above changes a wait from 500 (who knows the units?) to 5 * hz (5 seconds). I wonder if my physical host is just too slow to initialize everything in 500 and yours is not?
Can I ask what cpu you have in your host? Mine has an Opteron 4170 HE (getting a little long in the tooth…)
-
FWIW, i have the same problem with pfSense 2.3 and Window Server 2012, not R2.
-
FWIW, i have the same problem with pfSense 2.3 and Window Server 2012, not R2.
Had exact same problem (only 3 NICs detected, error above for the 4th) on Windows Server 2012 Hyper-V. Upgraded my server to Windows Server 2012 R2 and the problem was resolved.
-
The FreeBSD patch linked above changes a wait from 500 (who knows the units?) to 5 * hz (5 seconds). I wonder if my physical host is just too slow to initialize everything in 500 and yours is not?
Can I ask what cpu you have in your host? Mine has an Opteron 4170 HE (getting a little long in the tooth…)
I doubt it is timing related. It works fine for me even doing hyperv nested in VMware Workstation on a dual-core i5 processor. That has to have more latency/timing issues than your opteron….
To answer the actual question, my hyperv hosts are E3-1240v3 processors.
In relation to the other post, I have never tried it on 2012 R1 - I upgraded all those years ago, so don't have any left.
-
I have the exact problem. Windows Server 2012 (not R2).
The fourth NIC does not appear on pfSense.
Does anyone know how to patch/fix the kernel as per DD post (https://lists.freebsd.org/pipermail/svn-src-stable-10/2016-March/008308.html ) ????
I cannot upgrade my server to R2, since I don´t have license -
I am wondering what is the value of kern.hz on the affected installations.
This patch (https://lists.freebsd.org/pipermail/svn-src-stable-10/2016-March/008308.html) deals with the problem by making the time dynamic depending on kern.hz value instead of the, believed, default 100 kern.hz for VMs.
-
did you tried the patch?
can you provide instructions do apply it?
-
Have the similar problem on 2012 R2 after installing 2.3.2.
It seems that problem with NIC drivers and not enough cpu performance.
I have gigabyte brix which through hyper-v VLAN runs pfsense.After updating to latest realtek drivers and adding 1 core to VM, problem disappeared.
Just now tried to remove 1 core and VM did not detect any hn0, hn1, hn2 at all.on 2.2.6 everything was ok even with 1 core and old realtec drivers.
-
It seems like patch1 for 2.3.2 solved the problem.
Right now pfsense successfully started with 1 core, all NICs were detected. -
I have tried upgrading to 2.3. And I find that PFSense will not detect all NICS. I have now tried upgrading to 2.4 with the same outcome. I have also tried applying the above patch to 2.4 via the System Patches Package that I installed. However, when I test the packages, it states there is no file to patch
I cut and pasted the code from https://lists.freebsd.org/pipermail/svn-src-stable-10/2016-March/008308.html
and created three patches based on the 3 sections of code.Can anyone please advise how to apply this patch to 2.3 and or 2.4.
e.g.
/usr/bin/patch –directory=/ -t -p1 -i /var/patches/59f7b6a679008.patch --check --forward --ignore-whitespace
Hmm... Looks like a unified diff to me...
The text leading up to this was:-- stable/10/sys/dev/hyperv/netvsc/hv_rndis_filter.c Tue Mar 1 01:04:53 2016 (r296247)
+++ stable/10/sys/dev/hyperv/netvsc/hv_rndis_filter.c Tue Mar 1 02:07:14 2016 (r296248) No file to patch. Skipping... Hunk #1 ignored at 30. Hunk #2 ignored at 359. Hunk #3 ignored at 626. 3 out of 3 hunks ignored while patching 10/sys/dev/hyperv/netvsc/hv_rndis_filter.c done -
RESOLVED*****
Upgraded MS-Server 2012 to MS-Server2012R2 and everything now works as expected.
I have attempted to update a few MS-Server2012 Hyper-V PFSense firewalls and all have failed.
I will now update all HOST OS to 2012 R2.