2.4.0 interface issue
-
What type of interfaces are configured on the VM?
e1000? vmxnet3?
-
I'm using VMXNET3….
-
The kernel has vmxnet3 drivers built-in, so it doesn't make sense that they just wouldn't appear.
I have several VMs here with vmxnet3 and they're all fine. Are you certain they are vmxnet3?
-
At least that is what the Adapter Type says…
I typically use VMXNet3 as my network adapter type.
-
Also note that prior to update, VMWare Tools is installed….
-
This is happening to me as well, and I am using a normal piece of hardware: a J1900 machine.
-
So, I ended up installing a fresh setup of pfsense 2.4 then restore the config from xml file which worked.
I noticed a slower internet speed though, I'm on multi-wan (load balanced) setup with two 200Mbps FTTX lines and one 450Mbps leased line. The top speed I can get now is 400Mbps but slow down to 350Mbps.
I was getting like 700Mbps download speed before…
I will do more tests tomorrow to hopefully, rule out the issue.
-
@edan@aims.ac.th:
Also note that prior to update, VMWare Tools is installed….
Can you show me a screenshot of the network mismatch error?
I have several VMs configured in that way and they all work. The tools are not necessary for vmxnet3 on pfSense 2.3 and later, the drivers are built into the kernel.
-
This is happening to me as well, and I am using a normal piece of hardware: a J1900 machine.
Highly unlikely that is related, please start your own thread.
-
If a fresh install fixed it, I have to wonder if the upgrade failed somehow. It's possible you had a mismatch between the new kernel and the version of the pfSense module on the filesystem that caused the module to break and not find any interfaces.
-
With regards to the download speed. It appears that the new version of firefox slows the download.
Using other browsers like chrome and opera does not seem to limit the download so the speed issue can't be on PFSense.
The upgrade as seen from the GUI went well, the problem occurred after reboot. The interfaces are not detected and I was just prompted with setting the interfaces dialogs.
Anyway, as I was able to easily recover by installing from scratch and restore from backup xml file, everything is back to normal here.
