Please provide your feedback in this short Flings' survey.
Apr 30, 2019

I can successfully install the vib and can see my usb nics but I'm having issues with the persistence. When I assign as an uplink to one of the usb nics and reboot, I can no longer edit the usb uplink and it doesn't get identified as one but I still see the usb nics in the physical nics list. The same when I add in the persistence script provided, it doesn't recognize the uplinks and it doesnt allow me to make any networking changes related to the usb nic interfaces. The error message is "Failed - A specified parameter was not correct:".

This is installed on a nuc7i7bnh running esx 6.7.0 and a Startech Dual-NIC USB adapter. I am able to install the vib file alone via gui Package installer using the following path "/vmfs/volumes/datastore1/VMW_bootbank_vmkusb-nic-fling_0.8-1vmw.670.2.48.20124247.vib". Although the vib install says it fails in the gui, after the reboot I can see the usb nics. Server and networking in esxi is all default, the standard ports groups and virtual switches, nothing has been changed.

Any ideas?

May 09, 2019

If anyone has any issues with persistence and the error message I mentioned, adding the below lines to the script helped.

/etc/init.d/hostd restart
/etc/init.d/vpxa restart

I was able to edit the switch and adapter settings without any issues.

Thanks Songtao Zheng and William Lam for putting this together.

Apr 29, 2019

Can confirm the "TeckNet USB Network Adapter" from Amazon works well with this driver.
Installed on a HP ProDesk G1, running ESXi 6.7.0 (Build 8169922) as a home lab with no problems.

Apr 24, 2019

Intel NUC7i7BNH trying the Startech Dual-NIC USB-C. The driver installed but the adapter is not being recognized. Config is below - what else can I provide to try and troubleshoot?

[root@ASUAG1:~] vmware -vl
VMware ESXi 6.7.0 build-13006603
VMware ESXi 6.7.0 Update 2
[root@ASUAG1:~] chkconfig usbarbitrator --list
usbarbitrator on
[root@ASUAG1:~] lsusb
Bus 001 Device 004: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse
Bus 001 Device 003: ID 413c:2110 Dell Computer Corp.
Bus 001 Device 002: ID 413c:1010 Dell Computer Corp.
Bus 001 Device 001: ID 0e0f:8003 VMware, Inc. Root Hub
[root@ASUAG1:~] localcli system module list | grep usb
vmkusb_nic_fling true true
[root@ASUAG1:~] esxcli network nic list
Name PCI Device Driver Admin Status Link Status Speed Duplex MAC Address MTU Description
------ ------------ ------ ------------ ----------- ----- ------ ----------------- ---- ------------------------------------------------
vmnic0 0000:00:1f.6 ne1000 Up Up 1000 Full f4:4d:30:6f:8b:45 1500 Intel Corporation Ethernet Connection (4) I219-V

Apr 15, 2019

I'm using multiple dual-Gb NICs on a pile of NUC8i5BEH (and have tried NUC5i7RYH as well).
I'm using v1.0 of your Fling on vSphere 6.7u2, everything patched up to date.
(I've even reinstalled the NUC8s from scratch, which hasn't made any change)

If I use the Startech dual-Gb AX88179 NICs, everything works.
If I use the Vantec dual-Gb RTL NICs, I can't get any packets through them. But "esxcfg-nics -l" lists vusb0-vusb5 just as expected, and I can assign them to vmks and so on.

One possible give-away is that when I use the AX88179 NICs, they all report the CDP response from my Cisco SG300 and SG350 switches. With the RTL NICs connected to the same switches, they all say that CDP "is not available on this physical network adapter".

From doing a vmkping through an RTL NIC, the switch doesn't receive any unicast packets at all. Do the vmkping through an AX88179 NIC, the switch receives the unicast packet and the ping response is received by the ESXi host as you would expect.

And yes, I have checked that I'm not just getting the ports swapped over by mistake, and I've tried multiple NICs, multiple patch leads, multiple switch ports, multiple switches. I'm using simple vSwitches, not attempting vDS. :-)

Any ideas?


May 06, 2019

Hi JulesFM ,

Were you able to get the Startech nic's to persist and function after reboot? Anything special outside of what is in the instructions to get that to work?

Apr 23, 2019

Try forcing the switch port to 1000/Full instead of auto negotiating. I'm using a Realtek based USB NIC and I'm able to ping in both directions using a vmkernel port pinned to the NIC