Usbip error tcp connect

Проброс USB

Добрый день! Пытаюсь пробросить USB устройства (допустим сертификат, принтер) через usbip c Astra Linux Orel терминала как толстого клиента на терминальный сервер Astra Linux Orel, шарится нормально. Но с сервера не цепляется. Так же пробовал с wtware тонкого клиента шарить через BUS ID и цеплять, аналогично, если шарить с самого себя и подключаться к себе на сервер, то всё работает. Порт 3240 открыт везде. Выполняем подключение: usbip attach -r 192.168.0.40 -b 1-7 Ошибка: usbip: error: tcp connect При несуществующих ип адресах и где нет шары, ошибка эта же. Даже удалённо с сервера не отображает список юсб подключений, делаем: usbip list -r 192.168.0.40 получаем: usbip: error: could not connect to 192.168.0.40:3240: System error

На сервере и клиенте.

на сервере по 1 команде: root@ts1posh:/var/log# tcpdump -ni any port 3240 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes 13:46:17.615141 IP 192.168.0.35.55614 > 192.168.0.35.3240: Flags [P.], seq 3565525366:3565525445, ack 3547870498, win 23522, options [nop,nop,TS val 274418453 ecr 274416433], length 79 13:46:17.615279 IP 192.168.0.35.3240 > 192.168.0.35.55614: Flags [P.], seq 1:49, ack 79, win 546, options [nop,nop,TS val 274418453 ecr 274418453], length 48 13:46:17.615300 IP 192.168.0.35.55614 > 192.168.0.35.3240: Flags [.], ack 49, win 23522, options [nop,nop,TS val 274418453 ecr 274418453], length 0 13:46:17.615404 IP 192.168.0.35.55614 > 192.168.0.35.3240: Flags [P.], seq 79:127, ack 49, win 23522, options [nop,nop,TS val 274418453 ecr 274418453], length 48 13:46:17.615503 IP 192.168.0.35.3240 > 192.168.0.35.55614: Flags [P.], seq 49:110, ack 127, win 546, options [nop,nop,TS val 274418453 ecr 274418453], length 61 13:46:17.615514 IP 192.168.0.35.55614 > 192.168.0.35.3240: Flags [.], ack 110, win 23522, options [nop,nop,TS val 274418453 ecr 274418453], length 0 13:46:19.627161 IP 192.168.0.35.55614 > 192.168.0.35.3240: Flags [P.], seq 127:206, ack 110, win 23522, options [nop,nop,TS val 274420465 ecr 274418453], length 79 13:46:19.627339 IP 192.168.0.35.3240 > 192.168.0.35.55614: Flags [P.], seq 110:158, ack 206, win 546, options [nop,nop,TS val 274420465 ecr 274420465], length 48 13:46:19.627360 IP 192.168.0.35.55614 > 192.168.0.35.3240: Flags [.], ack 158, win 23522, options [nop,nop,TS val 274420465 ecr 274420465], length 0 13:46:19.627499 IP 192.168.0.35.55614 > 192.168.0.35.3240: Flags [P.], seq 206:254, ack 158, win 23522, options [nop,nop,TS val 274420465 ecr 274420465], length 48 13:46:19.627646 IP 192.168.0.35.3240 > 192.168.0.35.55614: Flags [P.], seq 158:219, ack 254, win 546, options [nop,nop,TS val 274420465 ecr 274420465], length 61

По второй tcp 0 0 0.0.0.0:3240 0.0.0.0:* LISTEN 1014/usbipd
tcp6 0 0 . 3240 . * LISTEN 1014/usbipd

На клиенте по первой tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes и всё висит

по второй — выполняешь а ответа от команды нет, сразу следующая пустая строка root@astra:/home/user# netstat -tulpn | grep 3240 root@astra:/home/user#

Источник

Facing issue to bind usb port to wsl2 #98

I read this blog to connect my USB device to wsl2 but got error
https://devblogs.microsoft.com/commandline/connecting-usb-devices-to-wsl/

The text was updated successfully, but these errors were encountered:

indicates that you may have a firewall issue. Are you running a third party firewall? If so, you need to open TCP port 3240 on your host. usbipd-win installs a Windows firewall rule for that, but not all third party firewalls honor those Windows rules.

Okay, I turned off the firewall,
Now it shows a different error

the error is only coming for the integrated webcam

That’s the wrong way around.

1. Stop service
2. Then run usbipd server Logging:LogLevel:Default=Trace
3. Finally, after getting the log, start the service again

Did you try to ‘attach’ while you were logging? This log is entirely empty. I need the log from the server while you reproduce the error you reported earlier.

Somehow it worked automatically after some tries, but now it’s showing the webcam in it’s list but can’t use it in applications

That error has been reported before, see #63.
The fact that attaches sometimes works, and sometimes does not is new information, thx.

Once the device is attached (and shows up in lsusb) it should work, but the standard WSL kernel probably does not have the Linux drivers. You will have to compile the WSL kernel with the right drivers, then your webcam should work normally.
See: https://github.com/dorssel/usbipd-win/wiki/WSL-support#building-your-own-usbip-enabled-wsl-2-kernel

I build the kernel, but the earlier error coming again

@sudip-mondal-2002
Please post the output of the following command

You are now facing issue #63. It can help to simply try attach again, or to unplug/replug the device, or to reboot the host. Unfortunately, this issue is tough to resolve.

Too bad. Other users had the System.IO.FileNotFoundException because of some incompatible software. But that does not seem to be your case. The only things I can advise:

• Try attach multiple times, other users (as well as yourself!) did get their device to attach after multiple attempts.
• Try unplugging/replugging the device
• Reboot the host

But your USB controller/drivers somehow seem incompatible with usbipd-win . However, you reported:

Somehow it worked automatically after some tries

So hopefully you can get it to work with a little trial and error.

Источник

usbipd: warning: A third-party firewall may be blocking the connection; ensure TCP port 3240 is allowed. #335

I have installed a clean WSL v2 ubuntu today. Windows 11 release branch all updates.

uname -r
5.10.102.1-microsoft-standard-WSL2

I installed usbipd-win 2.2.0 via MSI. Windows service is running.

I have a terminal window open so WSL is alive.

When I run «usbipd wsl attach —busid=5-1» I get the error:

usbipd: warning: A third-party firewall may be blocking the connection; ensure TCP port 3240 is allowed.
usbip: error: tcp connect
usbipd: error: Failed to attach device with BUSID ‘5-1’.

Since other posts here about this imply the firewall is blocking, I turned off my Windows firewall completely and re-ran. Same error.

Do you have any other troubleshooting steps?

The text was updated successfully, but these errors were encountered:

That means: not Microsoft & not usbipd-win.

Please turn back on Window firewall, as usbipd-win has installed a nice rule (as stated in the README).
You need to find out what other software is blocking the port and fix that.

That means: not Microsoft & not usbipd-win.

Please turn back on Window firewall, as usbipd-win has installed a nice rule (as stated in the README). You need to find out what other software is blocking the port and fix that.

I checked the firewall rule before testing with the firewall off for one test. And added another inbound allow rule when it didn’t work, without the local subnet restriction as the WSL2 ip appears in a different subnet.

No third party firewall/security software on this machine. We are running Microsoft Endpoint Protection which monitors things but has few settings enabled relating to the firewall other than for public networks.

without the local subnet restriction as the WSL2 ip appears in a different subnet

Your host and the WSL instance are in the same subnet.

settings enabled relating to the firewall other than for public networks

That may be the problem. Unfortunately, Windows regards the WSL network connection as public.

If this is the problem, then I should have said «not Windows, not usbipd-win», as Microsoft Endpoint Protection obviously is Microsoft.

I also kept getting this error. I do not and never have had a 3rd party firewall.

After much debugging, I figured out that the auto-installed windows firewall rule was for the temporary install path of usbip, ie C:UsersMeappdatablahtempblahusbipd.exe and not the correct path of the service that was running, ie C:Program Filesusbipd-winusbipd.exe

Once I manually deleted and re-added with the correct path, I can now connect ( well, I’ve gotten past the tcp error anyway.. *)

Seems like there’s a bug in the installer when locating the exe path.

*
OK I still get this the firewall error when doing usbipd wsl attach .. from the windows host, however, from within the WSL2 guest I can at least connect to the socket using usbip attach -r 10.0.0.10 -b 11-4

@Knio
Interesting. How did you install usbipd-win? (winget or msi). What version did you install? Did you update from version x to y?
You say:

temporary install path of usbip, ie C:UsersMeappdatablahtempblahusbipd.exe

The installer does not use a «temporary install path», it is fixed to %ProgramFiles% (unless you have specifically overridden that using the command line installer msiexec.exe ). Did you ever compile/run from code, or always used the released installer?

And about the *. Does usbipd wsl attach actually not work, or does it work and you just got this additional warning?

This was a fresh install using usbipd-win_2.2.0.msi on Microsoft Windows [Version 10.0.19043.1526] . No upgrade and I didn’t compile anything. Unfortunately I didn’t write write down the actual path but there was a definitely in appdata

Tried again. it eventually times out, and the guest does not see any devices:

However it does put the device into the ‘Shared’ state after that, and then I can connect with -r

@Knio
Thank for the report. Earlier you said:

I can at least connect to the socket using usbip attach -r 10.0.0.10 -b 11-4

but for wsl attach you get

What are the (exact) IP configurations of both the host and the WSL instance? It puzzles me why wsl attach does not work, but manual attach does. It looks as if WSL and the host can reach each other via 2 different IP addresses.

My windows host is 10.0.0.10 assigned from a normal home NAT DHCP; I have no idea how WSL2 networking works, but it’s a fresh Ubuntu-20.04 WSL2 guest.

(From windows) I can see that the service is listening:

(From windows) and even connect to it:

So it kinda seems like the client binary is blocked, or this is some other problem with how it communicates with wsl?

@Knio
Your WSL has address 172.23.43.103/20 , which is normal. Your host must also have an IP in this subnet. That is what usbipd is using. When you manually attach using 10.0.0.10 , then it is normal that the default firewall rule will block it, since it is not in the same subnet.

So that explains the difference: usbipd is trying to attach to 172. and manually you use 10.

Question is: why is 172. not working. What is the hosts network configuration?

I think you got it. the 172. interface is just blocked. TLDR seems to be microsoft/WSL#4139

And with -r 172.23.32.1 it fails, and I get this:

@Knio
That makes sense. But why is the default WSL host address not accepting? Probably because you had this odd firewall rule.
Can you try a ‘repair’ install of usbipd-win? Or else a re-install? Does it reproduce?

The firewall rule is created by the MSI installer, which is a standard WiX extension:

Lines 18 to 26 in 87876c9

This is something I haven’t seen failing before.

So, 1) running the msi again and doing a «repair» operation didn’t fix anything, but..
2) doing a full uninstall and reinstall and it works now. ¯_(ツ)_/¯
Thanks for all your help here.

@Knio
Thanks for testing. It appears to be a known WiX issue: wixtoolset/issues#5675
Still don’t know why the rule was screwed up initially, but it makes sense now that a repair (or update) won’t fix the issue. Since a reinstall did fix it, I will consider it a fluke. Not much can be done about it, maybe the soon to be released WiX 4 may fix it. I consider your (sub-)issue closed now.

@pilcherd
If you haven’t solved this issue by now, could you try a reinstall? Or can we close this issue?

Thanks again. Hopefully this thread is at least helpful for other people debugging.

Any human being who faces this issue again the FIX is so simple, this thing got me pulling my hair OUT tryna fix it

First try to turn your firewall off, disconnect from the internet temporarily while doing so and check if it works, if it does then you gotta add a rule(you can search that up in google)

If that still doesn’t work then turn your VPN off, my god damn VPN was causing all of these issues and I was pulling my hair out

If the above doesn’t work then
open task manager(ESC + SHIFT + CTRL) , click the performance tab, open resource monitor and click the Network tab
Then in the «TCP Connections» tab look for any program that has the same port, in this case 3240 that’s running, once you find it goto Task Manager find the same process name and terminate it(assuming that you couldn’t close it safely)

Hopefully no one would face this issue again

None of the above solutions have worked for me. Any updates?

@siddirp
What OS are you using, 10 or 11? Are you using any additional security software besides Windows firewall and Windows Defender? Have you checked that the firewall rule (as mentioned in the Readme) was correctly installed? Can you ping between your Windows host and the WSL instance, on their shared subnet?

All of these problems have been traced back to either of these causes.

Windows 11 Pro version 22H2. OS Build 22610.1. Do I need the Insiders build or anything like that?
I do not have any security software except what came with the OS.
I’m not savvy at Firewall work, but I didn’t see usbipd in the inboud or outbound rules. Is that where I am supposed to look? Is there another name I should look for?
I can ping both ways.

I suggest a repair install or uninstall/reinstall of usbipd-win. Someone else reported that the firewall rule wasn’t installed properly and that a reinstall fixed it. Everything else looks fine.

I have tried that several times, several versions.

Please check again if the firewall rule exists. It should be under incoming rules. What happens if you try to manually run usbip attach on WSL? Does the connection time out?

Ok, I feel really dumb. I had just reset Windows to a fresh state. I had been using usbipd-win for quite a while and was so confused why it wasn’t working after this reset. It turns out some 3rd party anti-virus stuff WAS installed and I had no idea. Sorry for all the bother!

I have a repaved as of yesterday win11 22h2 install that my company’s device mgmt story adds carbon black and defender for endpoint antivirus/antimalware services to. The firewall rule is present with correct path to the usbipd program executable that sets up tcp/3240 listener on windows side of things.

from windows 11 22h2 powershell 7.2.6 admin prompt i see

from wsl ubuntu 20.04 bash prompt i see

Question — Do we know at this point that it is carbon black, defender for endpoint, etc. antivirus/antimalware software that creates this unexpected usbipd: warning: A third-party firewall may be blocking the connection; ensure TCP port 3240 is allowed. result? If so i don’t have permissions to temporarily stop those antivirus/antimalware software packages when i need to use usbipd, is their another workaround?

@myusrn
The standard way of jailbreaking a locked down system is to «tunnel out and reverse proxy». Start the sshd service on the client (if not already running). From the Windows host ssh into the client with:

Then, on the client you can just use «127.0.0.1» as «remote host». E.g. usbip list -r 127.0.0.1 .

@dorssel
Thanks for the optional workaround to try. Is «client» in this case referring to the wsl distro that i want to project the physical host usb thumb drive into and «host» is the windows host that wsl distro is running on?

After running usbipd list -r 127.0.0.1 , presumably on windows host that the wsl distro is running on, do i then use usbipd.exe wsl attach —busid #-## -r 127.0.0.1 to project the usb thumb drive into the wsl distro instead of usbipd.exe wsl attach —busid #-## —distribution Ubuntu ?

When i execute usbipd.exe list -r 127.0.0.1 on windows 11 host i get an unrecognized command or argument result. Do i need to install a version other that usbipd-win, 2.3.0 to get support for that switch?

You’re mixing server and client. You need to run usbip list -r 127.0.0.1 (without the ‘d’ in usbip) on the client side.

Thanks for additional clarifications and details. Yes i was overlooking the difference between when i use windows host ‘usbipd.exe’ and when i use wsl distro client ‘usbip’ utility.

After establishing ssh connection from windows host to wsl distro, with tunnel reverse proxy setting enabled [ ssh @ -R 3240:127.0.0.1:3240 ] to jailbreak locked down system, i then executed the usbip list —remote 127.0.0.1 command which showed expected results but the usbip attach —busid #-## —remote 127.0.0.1 command and get a Device not found and Device in error state respectively for two different usb thumb drives i attempted to mount into wsl distro.

Perhaps those error messages relate to a well understood additional configuration step i overlooked or need to apply?

Note that my windows host has a usb thumb drive read-only policy. This hasn’t affected other scenarios where i project usb thumb drives into a virtualized environment for read-write access, e.g. virtual machine console | connect / disconnect from host.

@myusrn
Ah . SanDisk. See https://github.com/dorssel/usbipd-win/wiki/Tested-Devices.
Here’s the report, and some hints to maybe get them to work: #425. But in essence: SanDisk flash drives behave weird and usually don’t work with USBIP.

@dorssel
Thanks for the pointers to likely reasons behind this error result. In addition to my SanDisk Ultra Fit 32gb Usb3.0 and SanDisk Ultra Dual Drive 128gb Usb3.1g1 devices that generated those results i had an older SanDisk Cruzer Facet 16gb Usb2.0 available to try and it produced similar result.

I don’t currently have a laptop or dock Usb2.0 port to test if having the port vs the device restrict the Usb protocol version to 2.0 would make a difference with any of these devices. Sounds like one should pickup one of the tested Usb 3.x drive devices and vet setup with that first.

For those who use VPN, the simple solution for me was allowing local network traffic. For example, in Mullvad I had to go to «Settings -> VPN settings» and turn on «Local network sharing» toggle.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Страницы: [1]   Вниз

0 Пользователей и 1 Гость просматривают эту тему.

Страницы: [1]   Вверх

Время прочтения
5 мин

Просмотры 129K

Регулярно возникает задача подключения USB-устройства к удаленному ПК через локальную сеть. Под катом изложена история моих поисков в этом направлении, и путь к готовому решению на базе open-source проекта USB/IP с описанием заботливо установленных различными людьми на этом пути препятствий, а также способов их обхода.

Часть первая, историческая

Если машина виртуальная — всё это несложно. Функционал проброса USB от хоста в виртуалку появился еще в VMWare 4.1. Но в моём случае ключик защиты, опознающийся как WIBU-KEY, нужно было в разное время подключать к разным машинам, и не только виртуальным.
Первый виток поиска в далеком 2009-м году привел меня к железке под названием TrendNet TU2-NU4
Плюсы:

• иногда даже работает

Минусы:

• работает не всегда. Допустим, ключ защиты Guardant Stealth II через неё не заводится, ругаясь ошибкой «устройство не может быть запущено».
• ПО для управления (читай — монтирования и размонтирования USB-устройств) убого до крайности. Ключи командной строки, автоматизация — не, не слышали. Всё только руками. Кошмар.
• управляющее ПО ищет саму железку в сети широковещанием, поэтому работает это только в пределах одного broadcast-сегмента сети. Указать IP-адрес железки руками нельзя. Железка в другой подсети? Тогда у вас проблема.
• разработчики забили на устройство, слать баг-репорты бесполезно.

Второй виток случился во времена уже не столь отдаленные, и привел меня к теме статьи — USB/IP project. Привлекает открытостью, тем более, что ребята из ReactOS подписали им драйвер для Windows, так что теперь даже на x64 всё работает без всяких костылей вроде тестового режима. За что команде ReactOS огромное спасибо! Звучит всё красиво, попробуем пощупать, так ли оно на деле? К сожалению, сам проект тоже подзаброшен, и на поддержку рассчитывать не приходится — но где наша не пропадала, исходник есть, разберемся!

Часть вторая, серверно-линуксовая

Сервер USB/IP, расшаривающий USB-девайсы по сети, может быть поднят только в Linux-based OS. Ну что ж, линукс так линукс, устанавливаем на виртуалку Debian 8 в минимальной конфигурации, стандартное движение руками:

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install usbip

Установились. Дальше интернет подсказывает, что нужно бы загрузить модуль usbip, но — здравствуйте, первые грабли. Нет такого модуля. А всё оттого, что большинство руководств в сети относятся к более старой ветке 0.1.x, а в крайней 0.2.0 модули usbip имеют другие названия.

Поэтому:

sudo modprobe usbip-core
sudo modprobe usbip-host
sudo lsmod | grep usbip

Ну и добавим в /etc/modules такие строки, чтобы загружать их автоматически при старте системы:

usbip-core
usbip-host
vhci-hcd

Запустим сервер usbip:

sudo usbipd -D

Дальше всемирный разум нам подсказывает, что в комплекте с usbip идут скрипты, позволяющие нам управлять сервером — показать, какое устройство он будет расшаривать по сети, посмотреть статус, и так далее. Тут нас поджидает еще один садовый инструмент — эти скрипты в ветке 0.2.x, опять же, переименованы. Получить список команд можно с помощью

sudo usbip

Почитав описание команд, становится понятно, что для того, чтобы расшарить требуемый USB-девайс, usbip хочет узнать его Bus ID. Уважаемые зрители, на арене грабли номер три: тот Bus ID, который выдаст нам lsusb (казалось бы, самый очевидный путь) — ей не подходит! Дело в том, что железки вроде USB-хабов usbip игнорирует. Поэтому, воспользуемся встроенной командой:

user@usb-server:~$ sudo usbip list -l
 - busid 1-1 (064f:0bd7)
   WIBU-Systems AG : BOX/U (064f:0bd7)

Примечание: здесь и далее в листингах я буду всё описывать на примере моего конкретного USB-ключа. Ваши название железки и пара VID:PID могут и будут отличаться. Моя называется Wibu-Systems AG: BOX/U, VID 064F, PID 0BD7.

Теперь мы можем расшарить наше устройство:

user@usb-server:~$ sudo usbip bind --busid=1-1
usbip: info: bind device on busid 1-1: complete

Ура, товарищи!

user@usb-server:~$ sudo usbip list -r localhost
Exportable USB devices
======================
 - localhost
        1-1: WIBU-Systems AG : BOX/U (064f:0bd7)
           : /sys/devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb1/1-1
           : Vendor Specific Class / unknown subclass / unknown protocol (ff/00/ff)

Троекратное ура, товарищи! Сервер расшарил железку по сети, и мы можем её подключать! Осталось только дописать автозапуск демона usbip в /etc/rc.local

usbipd -D

Часть третья, клиентская и запутанная

Подключить расшаренное устройство по сети к машине под управлением Debian я попробовал сразу же на том же сервере, и всё прекрасно подключилось:

sudo usbip attach --remote=localhost --busid=1-1

Переходим к Windows. В моем случае это был Windows Server 2008R2 Standard Edition. Официальное руководство просит сначала установить драйвер. Процедура прекрасно описана в прилагаемом к windows-клиенту readme, делаем всё как написано, всё получается. На XP тоже работает без каких-либо трудностей.

Распаковав клиент, пробуем примонтировать наш ключик:

C:Program FilesUSB-IP>usbip -a %server-ip% 1-1
usbip err: usbip_network.c: 121 (usbip_recv_op_common) recv op_common, -1
usbip err: usbip_windows.c: 756 (query_interface0) recv op_common
usbip err: usbip_windows.c: 829 (attach_device) cannot find device

Ой-ой. Что-то пошло не так. Используем навык гугла. Встречаются отрывочные упоминания, что что-то там не так с константами, в серверной части разработчики при переходе на версию 0.2.0 изменили версию протокола, а вот в клиенте под Win сделать это забыли. Предлагаемое решение — поменяйте константу в исходнике и пересоберите клиент.

Вот только очень мне не хочется качать Visual Studio ради этой процедуры. Зато у меня есть старый-добрый Hiew. В исходнике константа объявлена как двойное слово. Поищем в файле 0х00000106, заменяя на 0х00000111. Не забываем, порядок байт обратный. Итог — два совпадения, патчим:

[usbip.exe]
00000CBC: 06 11
00000E0A: 06 11

Ииии… да!

C:Program FilesUSB-IP>usbip -a %server-ip% 1-1
new usb device attached to usbvbus port 1

На этом можно было бы закончить изложение, но музыка играла недолго. Перезагрузив сервер, я обнаружил, что устройство на клиенте не монтируется!

C:Program FilesUSB-IP>usbip -a %server-ip% 1-1
usbip err: usbip_windows.c: 829 (attach_device) cannot find device

И всё. На это мне не смог ответить даже всезнающий гугл. А при этом команда отобразить доступные на сервере устройства вполне корректно показывает — вот он, ключ, можете монтировать. Пробую примонтировать из-под Linux — работает! А если теперь попробовать из-под Windows? О ужас — это работает!

Грабли последние: что-то там в коде сервера не дописано. При расшаривании устройства он не считывает с него количество USB-дескрипторов. А при монтировании устройства из-под Linux, это поле заполняется. К сожалению, с разработкой под Linux я знаком на уровне «make && make install». Поэтому проблема решена с помощью довольно грязного хака — добавлением в /etc/rc.local

usbip attach --remote=localhost --busid=1-1
usbip port
usbip detach --port=00

Часть заключительная

После некоторых мытарств, это работает. Желаемое получено, теперь ключ можно примонтировать к любому ПК (и размонтировать, конечно же, тоже), в том числе — за пределами широковещательного сегмента сети. Если хочется — можно это сделать с помощью скрипта командной оболочки. Что приятно — удовольствие абсолютно бесплатное.
Надеюсь, что мой опыт поможет хабражителям обойти те грабли, которые отпечатались у меня на лбу. Спасибо за внимание!

The environment is

• Windows 10
• WSL2 Ubuntu 20.04 LTS

Mount USB to WSL

It’s easy to mount if it is just a USB drive that is shown on Windows e.g. E: or F:.

Let’s create a directory to mount the USB directory first. Then, mount it.

sudo mkdir /mnt/usb
sudo mount -t drvfs E: /mnt/usb

If you execute the following command, you can see the files on the USB stick.

ls -la /mnt/usb

Execute the following command if you want to umount it.

sudo unmount /mnt/usb

Setup usbipd-win

Install usbipd-win to the Windows machine

First, usbipd-win needs to be installed on your host machine before doing something on WSL.

1. Go to the release page of usbipd-win
2. Download msi and install it

You can see the following service after the installation.

> sc queryex usbipd

SERVICE_NAME: usbipd
        TYPE               : 10  WIN32_OWN_PROCESS
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
        PID                : 2032
        FLAGS

Preparation on WSL with Ubuntu

Execute the following command to install the necessary tools on WSL.

sudo apt update
sudo apt install linux-tools-virtual hwdata
sudo update-alternatives --install /usr/local/bin/usbip usbip `ls /usr/lib/linux-tools/*/usbip | tail -n1` 20

If you don’t update the package list by apt update, you could get the following error

$ sudo apt install linux-tools-virtual hwdata
[sudo] password for yuto:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
  libfwupdplugin1
Use 'sudo apt autoremove' to remove it.
The following additional packages will be installed:
  libdw1 linux-tools-5.4.0-125 linux-tools-5.4.0-125-generic linux-tools-common
The following NEW packages will be installed:
  hwdata libdw1 linux-tools-5.4.0-125 linux-tools-5.4.0-125-generic linux-tools-common linux-tools-virtual
0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
Need to get 6026 kB of archives.
After this operation, 27.9 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.ubuntu.com/ubuntu focal/main amd64 hwdata all 0.333-1 [23.3 kB]
Get:2 http://archive.ubuntu.com/ubuntu focal/main amd64 libdw1 amd64 0.176-1.1build1 [226 kB]
Get:3 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-tools-common all 5.4.0-125.141 [187 kB]
Get:4 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-tools-5.4.0-125 amd64 5.4.0-125.141 [5586 kB]
Get:5 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-tools-5.4.0-125-generic amd64 5.4.0-125.141 [1996 B]
Ign:6 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-tools-virtual amd64 5.4.0.125.126
Err:6 http://security.ubuntu.com/ubuntu focal-updates/main amd64 linux-tools-virtual amd64 5.4.0.125.126
  404  Not Found [IP: 91.189.91.39 80]
Fetched 6024 kB in 1s (4058 kB/s)
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/l/linux-meta/linux-tools-virtual_5.4.0.125.126_amd64.deb  404  Not Found [IP: 91.189.91.39 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Connect USB device to WSL

All commands in this section are on the host machine.

Check the device list

Let’s check how many devices are there and which one is what we want to connect.

> usbipd.exe wsl list
BUSID  VID:PID    DEVICE                                                        STATE
1-5    0b0e:245e  Jabra Link 370, USB Input Device                              Not attached
1-7    0408:5390  HP Full-HD Camera, HP IR Camera                               Not attached
1-8    06cb:00b7  Synaptics VFS7552 Touch Fingerprint Sensor with PurePrint...  Not attached
1-14   8087:0029  Intel(R) Wireless Bluetooth(R)                                Not attached
2-1    8087:0af1  HP GNSS Sensor                                                Not attached
2-2    8087:0aca  USB Serial Device (COM5), USB Serial Device (COM4), Modem...  Not attached
2-3    8087:0ac9  Intel(R) XMM(TM) 7360 LTE-A                                   Not attached
6-2    05e0:1200  USB Input Device                                              Not attached
6-5    2109:8888  USB Billboard Device                                          Not attached
7-3    0bda:8153  Realtek USB GbE Family Controller                             Not attached
9-1    0c45:7638  USB Input Device                                              Not attached
9-5    03f0:0269  HP Thunderbolt Dock Audio Headset, USB Input Device           Not attached
9-7    03f0:0667  WinUSB, USB Input Device                                      Not attached
10-1   2149:2306  USB Input Device                                              Not attached

In my case, 6-2 is what I want. It’s a scanner.

Attach the desired device to WSL

But I got this error.

> usbipd.exe wsl attach --busid 6-2
usbipd: info: Using default WSL distribution 'Ubuntu-20.04'; specify the '--distribution' option to select a different one.
usbipd: error: Access denied; this operation requires administrator privileges.
usbipd: info: The first time attaching a device to WSL requires elevated privileges; subsequent attaches will succeed with standard user privileges.

I got the following error if I executed it with an Admin user.

> usbipd.exe wsl attach --busid 6-2
usbipd: error: There are no WSL distributions installed; see https://docs.microsoft.com/windows/wsl/basic-commands#install on how to install one.

Because I installed WSL on my own user but not on the Admin user. The Admin user doesn’t have WSL.

In this case, you can’t execute the command even if you try the following command. The domain name and user name are replaced with a placeholder here.

> runas /profile /user:<Domain name><User Name> "usbipd.exe wsl attach --busid 6-2"
Enter the password for <Domain name><User Name>:
Attempting to start usbipd.exe wsl attach --busid 6-2 as user "<Domain name><User Name>" ...

This command fails. A new window appears but is closed immediately.

usbipd: warning: A third-party firewall may be blocking the connection; ensure TCP port 3240 is allowed.

The account must be in the Administrator group. I executed the following command after putting my account into the Administrator group.

> usbipd.exe wsl attach --busid <busid>
usbipd: info: Using default WSL distribution 'Ubuntu-20.04'; specify the '--distribution' option to select a different one.
usbipd: warning: A third-party firewall may be blocking the connection; ensure TCP port 3240 is allowed.
usbip: error: tcp connect
usbipd: error: Failed to attach device with busid '6-2'.

But this error above is thrown…

Hmm… I don’t have a right to turn off Firewall. I uninstalled usbipd-win and re-installed it but it didn’t work for me.

Hack to connect the desired device to WSL without Admin privilege

Let’s cheat here. If you connect to the WSL from the host machine via ssh, you can ignore the firewall settings.

Start SSH server on WSL

All commands are on WSL here.

Execute the following command on WSL to check the content of ssh connection config.

cat /etc/ssh/sshd_condig

Then, you will see the following.

PasswordAuthentication no

Change it to yes and save it.

PasswordAuthentication yes

Then, execute the following command. The server will start.

$ sudo service ssh restart
* Restarting OpenBSD Secure Shell server sshd

Connect to WSL via SSH from the Host machine

The format to connect via SSH is the following.

ssh <username>@<IP address of WSL> -R 3240:127.0.0.1:3240

You can check the IP address on WSL with ip a command. The IP address is shown on inet for eth0.

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 6e:27:82:86:7d:6e brd ff:ff:ff:ff:ff:ff
3: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 56:5a:7d:9f:42:5d brd ff:ff:ff:ff:ff:ff
4: [email protected]: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/ipip 0.0.0.0 brd 0.0.0.0
5: [email protected]: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/sit 0.0.0.0 brd 0.0.0.0
6: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:15:5d:1c:7f:e0 brd ff:ff:ff:ff:ff:ff
    inet 172.23.31.247/20 brd 172.23.31.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::215:5dff:fe1c:7fe0/64 scope link
       valid_lft forever preferred_lft forever

Let’s connect to the WSL from the host machine via SSH.

> ssh [email protected] -R 3240:127.0.0.1:3240
[email protected]'s password:
Welcome to Ubuntu 20.04.5 LTS (GNU/Linux 5.10.102.1-microsoft-standard-WSL2 x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

  System information as of Tue Nov 15 15:58:58 CET 2022

  System load:  0.0                Processes:             36
  Usage of /:   1.1% of 250.98GB   Users logged in:       0
  Memory usage: 9%                 IPv4 address for eth0: 172.23.31.247
  Swap usage:   0%

  => There is 1 zombie process.


0 updates can be applied immediately.



The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

It could connect to WSL.

Show the available devices and try to connect the device to WSL

I could see the following result when executing the following command on WSL.

$ usbip list -r 127.0.0.1
Exportable USB devices
======================
 - 127.0.0.1
        1-1: Symbol Technologies : Bar Code Scanner (05e0:1200)
           : USBVID_05E0&PID_1200S/N:38B63F28B0A967459FDC95404F7D3524:3
           : (Defined at Interface level) (00/00/00)
           :  0 - Human Interface Device / Boot Interface Subclass / Keyboard (03/01/01)

        6-2: Symbol Technologies : Bar Code Scanner (05e0:1200)
           : USBVID_05E0&PID_120022222523070578__
           : (Defined at Interface level) (00/00/00)
           :  0 - Human Interface Device / Boot Interface Subclass / Keyboard (03/01/01)

Yes!! No more connection errors here!!

However… it doesn’t work for this scanner at all…

$ usbip attach -b 6-2 -r 127.0.0.1
usbip: error: import device

Oooooops… Lost my day…

According to the wiki page of usbipd-win, some devices can’t be used…