I have a problem that my nics show a message on two of my "servers"...
similiar to - https://flings.vmware.com/usb-network-native-driver-for-esxi/comments/14247#comment_14413 -

2021-10-08T06:41:28.300Z cpu2:2097562)WARNING: usb_proc_free:249: failed to destroy world 2109433: Not found
2021-10-08T06:41:29.104Z cpu2:2097562)cdce_attach: usbd_transfer_setup success with alt error 12
2021-10-08T06:41:29.104Z cpu2:2097562)cdce_attach: usbd_transfer_setup success with alt 1
2021-10-08T06:41:29.104Z cpu1:2097590)DMA: 679: DMA Engine 'vusb0-dma-engine' created using mapper 'DMANull'.
2021-10-08T06:41:29.105Z cpu1:2097590)Uplink: 13962: Opening device vusb0
2021-10-08T06:41:29.105Z cpu0:2097207)Uplink: 13811: Detected pseudo-NIC for 'vusb0'
2021-10-08T06:41:38.613Z cpu2:2097207)NetqueueBal: 4970: vusb0: new netq module, reset logical space needed
2021-10-08T06:41:38.613Z cpu2:2097207)NetqueueBal: 4999: vusb0: plugins to call differs, reset logical space
2021-10-08T06:41:38.613Z cpu2:2097207)NetqueueBal: 5035: vusb0: device Up notification, reset logical space needed
2021-10-08T06:41:38.613Z cpu3:2109774)NetSched: 654: vusb0-0-tx: worldID = 2109774 exits
2021-10-08T06:44:15.662Z cpu3:2097562)DMA: 724: DMA Engine 'vusb0-dma-engine' destroyed.
2021-10-08T06:44:15.662Z cpu3:2109788)NetSched: 654: vusb0-0-tx: worldID = 2109788 exits

those repeat after each message block...
Any idea on how to solve those...
I use different nic vendors but with the same Realtek RTL8156 chipset.
My ESXi version is 6.7.0 with a Build 15160138 on both servers.

Has any one tried the 1.8 USB Fling driver with 7.0 U3

When I'm building the ISO to do the upgrade, I get this error:

PS C:\users\username\Desktop\build> Add-EsxSoftwareDepot .\ESXi702-VMKUSB-NIC-FLING-47140841-component-18150468.zip

...

PS C:\users\username\Desktop\build> Add-EsxSoftwarePackage -ImageProfile $newProfile -SoftwarePackage "vmkusb-nic-fling"
Add-EsxSoftwarePackage : VIB VMW_bootbank_vmkusb-nic-fling_1.8-3vmw.702.0.20.47140841 requires vmkapi_incompat_2_8_0_0, but the requirement cannot be satisfied within the ImageProfile. However, additional VIB(s)
VMware_bootbank_esx-base_7.0.2-0.25.18538813, VMware_bootbank_esx-base_7.0.2-0.0.17867351, VMware_bootbank_esx-base_7.0.2-0.20.18426014, VMware_bootbank_esx-base_7.0.2-0.15.18295176 from depot can satisfy this requirement.
At line:1 char:1
+ Add-EsxSoftwarePackage -ImageProfile $newProfile -SoftwarePackage "vm ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (VMware.ImageBuilder.Types.ImageProfile:ImageProfile) [Add-EsxSoftwarePackage], Exception
+ FullyQualifiedErrorId : EsxImageProfileValidationError,VMware.ImageBuilder.Commands.AddProfilePackage

It looks like an updated to the driver is required?

Fling is NOT supported with 7.0 Update 3 (yet)

You will always need a new version of the Fling for major releases, which includes U-releases

Understood William. I assumed that to be the case, but wanted to pop somerthing up on the Comments section so others are aware. Thanks for the quick response. Look forward to seeing the next release of Fling :-)

i Have:

NUC10i7FNH
ESXi 6.7 (lasted fling update from this site for 6.7)
2x QNAP QNA-UC5G1T (latest firmware)
Synology NAS DS920+ (lasted driver update for the qnap)

The connections goes down every 5-7 days, anyone runs into similar problem?

Experiencing similar issues!

Running Version: 7.0.2 Build: Releasebuild-17867351 w/ a TP-Link UE300 adapter.

[root@localhost:~] esxcli software vib install -d /vmfs/volumes/datastore1/ESXi702-VMKUSB-NIC-FLING-47140841-

component-18150468.zip

[DependencyError] VIB Realtek_bootbank_r8152_2.06.0-4 requires com.vmware.driverAPI-9.2.3.0, but the requirement

cannot be satisfied within the ImageProfile.

VIB Realtek_bootbank_r8152_2.06.0-4 requires vmkapi_2_3_0_0, but the requirement cannot be satisfied within the

ImageProfile. Please refer to the log file for more details.