This is great to see, but I also really would love to see MTU being able to be set on this driver.

Yes, this is already in the backlog :)

I was able to install it and I can see the adapter via lsusb, but it never shows up in the NIC list:

[root@esx01:/etc/rc.local.d] lsusb
Bus 001 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Bus 001 Device 003: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 0e0f:8003 VMware, Inc.

root@esx01:/etc/rc.local.d] 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 54:b2:03:0b:86:e6 1500 Intel Corporation Ethernet Connection (2) I219-V

I am also in this camp, as are several posters in this thread. Is there an issue with the driver? an adapter revision on the chipset? Perhaps we're simply missing something?

lsusb identifies the device, but listing NIC in system reveals only the onboard Intel one (NUC)

@Ei @SqillyBDuillions,
Do you still have such issue?
The device should be supported, can you help to double check with
'vmkload_mod -l | grep usb'

Thanks,
Songtao

Songtao:

I got extensive help from
Jose J Gomes

You can follow the trail here:

https://github.com/gomesjj/r8152/issues/1#issuecomment-499861433

I suspect the USB NIC I'm using, is simply not supported (officially?) yet.

Thanks to Jose and many emails and messages back and forth, it's now working.

" am really happy the driver is working for you.

The one thing I noticed re-reading the thread on GitHub is that at some point you updated the VIB from 2.06 to 2.11; I had seen that to cause the driver not to load anymore at boot, but now I realise what causes the issue (usbnet won’t load). Thanks to you, I’ve learned something new. ?

Why the driver did’t work after you clean installed is a puzzle though… However, please do not update the VIB in the future (unlikely, I know); uninstall, reboot and then install the new VIB.

Regarding further ESXi updates, they should work OK, as I have performed multiple ones without an issue. An update will not remove the VIB or otherwise re-enable the vmkusb module.

The one thing to look for will be the next major upgrade to ESXi as VMware is preparing to completely remove support for the legacy drivers. Hopefully the vmkusb-nic-fling will improve and eventually USB Ethernet will become native on ESXi…"

I believe he will be publishing a new custom VIB eventually.

Thank you for the feedback and glad it works for you.
Also Thanks Jose on the help, and he also feedback for more devices support which we have added (upto 14 devices now, see the requirement tab) in the new version update.

Well hopefully the latest model, TPLINK UE300 is included, I look forward to it.

Although, considering the trouble I had, I'm reluctant to update, for the time being!

Thanks for the hard work, it's appreciated.

I've got a Realtek 8153 USB3 dual NIC and have followed instructions. Sometimes after loading ESXi 6.7, it gives the no supported adapter found. Most of the time, it loads fully and recognizes the NICs, however. DHCP doesn't work, but static assignment works. Good so far.

A problem I haven't been able to solve yet though is with the USB persistence on bootup and connecting the physical adapters to the vswitch where management exists. Having the lines from the instructions in local.sh seems like it would help, but I've found that link detection isn't reliable in my configuration. When one NIC is physically plugged in, vusb0 and vusb1 both show "Link Detected: True" and "Link Status: Up". Also, I can't get vusb0 NIC to work regardless of static IP when connected to vswitch0. If I change physical cabling over to vusb1 and change config again, it works. After a reboot, no mix of vusb0 or vusb1 in the local.sh script seems to help.

Thanks guys for your work on this!

Hi Ben,

Try adding the "restart" lines shown below, this helped me with the persistence issues I was having. Also, make sure the interface names (vusbX) and vswitch reflect what you have configured in esx.

if [ "${vusb0_status}" = "Up" ]; then
esxcfg-vswitch -L vusb0 vSwitch0
esxcfg-vswitch -M vusb0 -p "Management Network" vSwitch0
esxcfg-vswitch -M vusb0 -p "VM Network" vSwitch0
/etc/init.d/hostd restart
/etc/init.d/vpxa restart
fi

Hello,

Thanks a ton for this Fling.

I was able to install it and I can see the adapter via lsusb, but it never shows up in the NIC list:

[root@esx01:/etc/rc.local.d] lsusb
Bus 001 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Bus 001 Device 003: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 0e0f:8003 VMware, Inc.

root@esx01:/etc/rc.local.d] 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 54:b2:03:0b:86:e6 1500 Intel Corporation Ethernet Connection (2) I219-V

Any suggestions?

Thanks,

E!

I am also in this boat as is several others in this thread, except the TPLink device for me, what are we missing? Did you solve this?