Replies: 2 comments
-
You are correct. |
Beta Was this translation helpful? Give feedback.
-
I also hope to find a suitable Windows client software. I tried usbip-win and it worked fine. I shared a COM device within the LAN using usbipd-win. With usbip-win connection, it can be used successfully without enabling testsigning. Command Reference: Server: winget install usbipd
# Found device busid or vid:pid
usbipd list
# Share my ESP32 com
usbipd bind -i 1a86:7523 Client: # Download and unzip usbip-win
# https://github.com/cezanne/usbip-win/releases/download/v0.3.6-dev/usbip-win-0.3.6-dev.zip
usbip.exe install
# List shared devices on the server
usbip.exe list -r 192.168.0.100
# Attach device
usbip.exe attach -r 192.168.0.100 -b 3-2
# Show imported USB devices
usbip.exe port
# Detach device
usbip.exe detach -p 00 Additionally, you can also take a look at usbip-win2, which reportedly includes a GUI. However, I haven't tested it myself because my device cannot enable testsigning. |
Beta Was this translation helpful? Give feedback.
-
Hello Frans,
it is unclear to me if usbipd-win is suitable for my use case: I want to remote a digicert code signing usb token to a windows build vm. I don't care if the server side is running on windows or linux, but I need client side access from a windows 10 build vm to the server running usbipd-win or similar.
What I haven't understood is: Does the downloadable MSI of yours only supply the server side of USB-remoting or does it contain the necessary software for clients as well? If not, can you recommend a client package for windows? From my investigations so far, all IP/USB windows based drivers are in not so a mature state, lots haven't been updated for ages and some lack properly signed drivers. Can you share your experience? Stability is of uttermost importance for my build VMs.
Any help appreciated,
--
Stefan
Beta Was this translation helpful? Give feedback.
All reactions