Is there any way to keep the BUSID fixed

[baichengchen72-alt]

If my system restarts or re unplugges the same USB device, the BUSID will change, causing the client to use it synchronously. Is there any way to keep the BUSID fixed

[dorssel]

The BUSID on the host side is supposed to be fixed already. I.e., the same port on the same hub should already have a stable BUSID. If it does not, then there may be something wrong with your USB stack and/or HUB drivers. The host (usbipd-win) does not influence / cannot control the assigned BUSID on the client side. Usually, clients just assign those sequentially in the order of attachment.

[jankapte]

The problem is rather that while the BUSID is fixed on the host side, everytime detaching and attaching the same device increases the BUSID in the client.

This is a major problem with devcontainers, because assuming a USB device with BUSID 1-12 (in Windows), results in /dev/bus/usb/001/002 on build-time of the devcontainer, but after unplugging and replugging, and re-attaching, the BUSID increases to /dev/bus/usb/001/003 in WSL - but this change is not present intisde the devcontainer, it continues to show /dev/bus/usb/001/002 which does not exist anymore...

Idk how to solve that. It's not feasible to rebuild the container every time the USB device got re-plugged.