Hi, great project.
i have installed
vmkusb-nic-fling 1.11-1vmw.800.1.20.61054763 VMW VMwareCertified 2023-01-15

How I do an update to the latest version. I dknt want to uninstall an reinstall. Is there an update possible?

Im playing with the different versions and I will try to update the esx system to
ESXi-Version 8.0.1
Hypervisor VMware ESXi
Build 22088125

Is there a fling version fling version which will be compatible?

If I try to upgrade and I get the following error. Do I have to remove the vib, run the esx update and install again?

esxcli software vib update -d ESXi80U1-VMKUSB-NIC-FLING-64098092-component-21669994.zip
[DependencyError]
On platform embeddedEsx, VIB VMW_bootbank_vmkusb-nic-fling_1.12-1vmw.801.0.0.64098092 requires vmkapi_incompat_2_11_0_0, but the requirement cannot be satisfied within the ImageProfile.
On platform embeddedEsx, VIB VMW_bootbank_vmkusb-nic-fling_1.12-1vmw.801.0.0.64098092 requires vmkapi_2_11_0_0, but the requirement cannot be satisfied within the ImageProfile.

I bought some new hardware, mini pc's running the Intel i226 Chipset. Tested on ESXI 8 and NIC's work OOB however, all previous ESXI releases the NIC won't work on.

Is it possible to extract the working driver for i226 from the ESXI 8 build and inject into 6-7 to 7 builds?

Nevermind. I used the 7.0U3 and it already had the i226 driver and worked perfect.

Hi, Esxi 8.0 U1C - (Ver:22088125) (image based LifeCycle Controller) listing the Fling version 1.16 from April, 2023, but when selecting "Add components" then only 0.4 is available from 2020.
I tried to build my custom image for an USB NIC as per recommendation, but can't.
Please advise.
Thank you

Hi,
actually there is no ESXi 8.0U1C compatible version, check the fling and ESXi release notes as this might change in the future.

In April 2023 there was no fling version 1.16 published(?)

Of course, a fling duration of four years is very long. usb is a mess. That‘s it. That‘s the message.

Happy that the fling team still finds inter-solutions for all challenges chipset, tpm, speed, jumbo frames, persistence, backward compatibility, etc.

Custom images contain closed-source components. The actual builder does not update/create all lists for IP, EULA, etc. However only in this sense Lifecycle Controller images become true full-managed.

just wanted to thank you for this awesome fling!
The StarTech.com US1GC30B with chipset RTL8153 works flawlessly!