Ability to connect WSL to remote USB interfaces with Digi Anywhere USB
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
Problem: need to test embedded devices located in a lab, while using WSL2. The lab has Digi's AnywhereUSB devices.
1) cannot use USBIPD (it does not recognize the remote hub as a usb hub)
2) cannot use Digi's debian package on WSL
3) cannot export serial ports directly from Windows11 to WSL
**Describe the solution you'd like**
A standard way to be able to use kernel drivers and, hopefully, some of the well-known drivers available as modules.
and/or
A way to fix USBIPD to recognize remote hubs or at least remote ports or remote devices.
**Describe alternatives you've considered**
Tried to "make" Digi's AnywhereUSB RealPort debian package, it fails on WSL
Tried connecting the usb port from windows to WSL, usbipd fails.
Tried mapping a serial port directly, it fails (the remote device is an FTDI cable and it cannot map the serial port to one that WSL sees directly).
**Additional context**
Win11, WSL2, Ubuntu - attempting to use a remote usb-to-serial FTDI cable connected to a Digi AnywhereUSB remote USB hub.
Port connects fine to the win11 host, just not to Linux.
```
C:\>usbip list
Connected:
BUSID VID:PID DEVICE STATE
0403:6001 USB Serial Converter Incompatible hub
...
```
Contributor guide
Research direction
Start by reproducing the WSL2 setup with a Digi AnywhereUSB remote hub and the remote FTDI cable, then run `usbip list` to confirm the reported `Incompatible hub` state. Done would mean a standard WSL path can access the remote USB device, or usbipd recognizes the remote hub, ports, or devices.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, ubuntu
- Domain
- embedded-iot, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100