usb-remote
Client-server software to share USB devices over the network.
| Source | https://github.com/epics-containers/usb-remote |
|---|---|
| PyPI | uvx usb-remote --version |
| Docker | docker run ghcr.io/epics-containers/usb-remote:latest |
| Documentation | https://epics-containers.github.io/usb-remote |
| Releases | https://github.com/epics-containers/usb-remote/releases |
Overview
usb-remote allows USB devices to be easily discovered and shared over a network using the USB/IP USB-over-Ethernet service.
A usb-remote server runs on a machine with physical USB devices attached and shares its devices to clients. Clients can connect to multiple servers to access and control their USB devices as if they were locally connected.
Comparison to Digi's AnyWhereUSB
usb-remote is a FOSS alternative to commercial USB-over-Ethernet solutions like Digi's AnyWhereUSB.
Advantages of Digi's AnyWhereUSB:
- Commercial product with support and warranty
- Dedicated hardware servers for USB device sharing
- Excellent security features controlling access to USB devices
Advantages of usb-remote:
- Good support for UVC isochronous Webcams that do not work with AnyWhereUSB
- Very simple to setup and use in trusted network environments
- Free and open source software (FOSS)
- The server runs on standard hardware such as a $55 Raspberry Pi
Installation
See the Server Setup and Client Setup guides for installation instructions.
Example Client Commands
# List devices on all configured servers
usb-remote list
# List devices on a specific server
usb-remote list --host raspberrypi1
# Attach a device my description substring
# (scans all servers, fails on multiple matches)
usb-remote attach --desc "Camera"
# Attach first matching device across servers
usb-remote attach --desc "Camera" --first
# Attach a device based on serial number - recommended to guarantee unique match
usb-remote attach --serial=1272D8DF
# Detach a device
usb-remote detach --serial=1272D8DF
# Find devices on the 1-4 bus of a specific server, using a glob pattern
usb-remote list --host raspberrypi1 --bus '1-4-*'
Search Arguments:
--desc TEXT: substring or glob pattern to match device description--serial TEXT: glob pattern to match device serial number--bus TEXT: glob pattern to match USB bus ID (e.g.1-4.3)--host TEXT: search a single server by hostname or IP address
Architecture
See the Architecture Reference for full details.
See https://epics-containers.github.io/usb-remote for more detailed documentation.
Metadata
Release files for usb-remote 2.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| usb_remote-2.3.2.tar.gz | 6.8 MB | Without provenance | Details for usb_remote-2.3.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| usb_remote-2.3.2-py3-none-any.whl | Python 3 | none | any | Details for usb_remote-2.3.2-py3-none-any.whl |
Total release size: 6.8 MB
Release files / usb_remote-2.3.2.tar.gz
| Download URL | usb_remote-2.3.2.tar.gz |
|---|---|
| Size | 6.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5f8b56bbad14e7786d9eacf2f1f68dcf409f084ced29020b49194cbc6c4ed37c
|
|
BLAKE2b-256 checksum How to use checksums |
d6c44eda3c033ffadca2a7b45e9cd61a9f3b1410d7b11c17fe0a29fa6b112500
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / usb_remote-2.3.2-py3-none-any.whl
| Download URL | usb_remote-2.3.2-py3-none-any.whl |
|---|---|
| Size | 36.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
52363de98fc5da0f8745ddbd5a1d60fe15f5a7a1809c93ba8e1f3bb6f98d1acd
|
|
BLAKE2b-256 checksum How to use checksums |
59e05fd45718967f9a604a3487f98c906672150386c782abf683f89af75a6032
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for usb-remote 2.3.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.