[How-To] Using VMXNET2/3 NICs in pfSense 2.0
-
Hi,
I am trying to get my VM working on VMXNET3 but pfSense won't detect the NICs. VMXNET2 NICs are identified and I can use them but I want to switch to VMXNET3.I am running a AMD64 2.0.1 pfSense version on a VM with 8GB RAM.
The guide in this thread works but for VMXNET2 only. Are there an special 64-bit drivers for VMXNET3?
-
so you installed the native tools from vmware? This would have the drivers - Mine sees the nics, but I am running 32bit of pfsense.
vmx3f0: flags=8802 <broadcast,simplex,multicast>metric 0 mtu 1500
options=403bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4,tso6,vlan_hwtso>ether 00:0c:29:1e:18:90
media: Ethernet 10Gbase-T
status: active
vmx3f1: flags=8802 <broadcast,simplex,multicast>metric 0 mtu 1500
options=403bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4,tso6,vlan_hwtso>ether 00:0c:29:1e:18:9a
media: Ethernet 10Gbase-TI just don't currently have them enabled because I don't see any point to using them and had issues with vpn outbound from client inbound when they were being used.</rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4,tso6,vlan_hwtso></broadcast,simplex,multicast></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4,tso6,vlan_hwtso></broadcast,simplex,multicast>
-
You'll have to patch some wrong assumptions in pfsense code about how interfaces are named.
Unfortunately, vmxnet3 creates somewhat odd named interface names with a number in them, and
the 2.0.1 code assumes that as soon as an interface name contains a number, that's the start of the
interface number, as in "re3" being the 3rd unit of the "re" driver. Check this whole thread,
the required fixes are already described here.This is fixed in 2.1.
About the issue of the missing libraries: instead of symlinking, you can also put the following statement
into /usr/local/etc/rc.d/vmware-tools.sh at the beginning (but of course after the #!/bin/sh line):/sbin/ldconfig -m /usr/local/lib/compat
Cheers,
Markus -
yeah I am running 2.1.. so explains why I don't have any issues with them.
-
ok I had missed the amd64 part.
New problem now. I see the new vmxnet3 NICs and I assign them the IP addresses just like the earlier NICs. Even the WAN gets the internet IP. But I cannot access or even ping the pfSense IP address after that. They become totally unresponsive. Don't see this issue with vmxnet2 -
And is the nic using vmx3 connected in your esxi settings?
-
Not sure what you mean by connected in esxi settings.
Just like changing to vmxnet2 I shut down the vm, edit settings, remove old NICs and add new vmxnet3. Reboot the vm, assign IP address to the interfaces. Thats it.
-
In your settings for your nic - there is a connected checkbox, and connect on power on checkbox.
-
Of course all NICs are connected. How would I see the NICs during boot if they weren't connected.
