Not working yet
~# cat /etc/opkg.conf
dest root /
dest ram /tmp
lists_dir ext /var/opkg-lists
option overlay_root /overlay
option check_signature
arch all 100
arch arm_cortex-a9_vfpv3-d16 200
~# opkg info libudev
Package: libudev
Version: 3.2-1
Depends: libc
Status: install user installed
Architecture: arm_cortex-a9_vfpv3
Installed-Time: 1591553874
~# opkg list-installed
announce - 1.0.1-1
base-files - 204.2-r11063-85e04e9f46
block-mount - 2020-05-12-84269037-1
busybox - 1.30.1-5
cgi-io - 19
dnsmasq - 2.80-16.1
dropbear - 2019.78-2
e2fsprogs - 1.44.5-2
firewall - 2019-11-22-8174814a-1
fstools - 2020-05-12-84269037-1
fwtool - 2
getrandom - 2019-06-16-4df34a4d-3
hd-idle - 1.05-2
hostapd-common - 2019-08-08-ca8c2bd2-3
ip6tables - 1.8.3-1
iperf3 - 3.7-1
iptables - 1.8.3-1
iw - 5.0.1-1
iwinfo - 2019-10-16-07315b6f-1
jshn - 2020-02-27-7da66430-1
jsonfilter - 2018-02-04-c7e938d6-1
kernel - 4.14.180-1-a92a3f5c5bed2671533484c7ace9d5b5
kmod-bluetooth - 4.14.180-1
kmod-btmrvl - 4.14.180-1
kmod-cfg80211 - 4.14.180+4.19.120-1-1
kmod-crypto-aead - 4.14.180-1
kmod-crypto-cmac - 4.14.180-1
kmod-crypto-crc32c - 4.14.180-1
kmod-crypto-ecb - 4.14.180-1
kmod-crypto-ecdh - 4.14.180-1
kmod-crypto-hash - 4.14.180-1
kmod-crypto-kpp - 4.14.180-1
kmod-crypto-manager - 4.14.180-1
kmod-crypto-null - 4.14.180-1
kmod-crypto-pcompress - 4.14.180-1
kmod-fs-ext4 - 4.14.180-1
kmod-gpio-button-hotplug - 4.14.180-3
kmod-hid - 4.14.180-1
kmod-input-core - 4.14.180-1
kmod-input-evdev - 4.14.180-1
kmod-ip6tables - 4.14.180-1
kmod-ipt-conntrack - 4.14.180-1
kmod-ipt-core - 4.14.180-1
kmod-ipt-nat - 4.14.180-1
kmod-ipt-offload - 4.14.180-1
kmod-lib-crc-ccitt - 4.14.180-1
kmod-lib-crc16 - 4.14.180-1
kmod-mac80211 - 4.14.180+4.19.120-1-1
kmod-mmc - 4.14.180-1
kmod-mwifiex-sdio - 4.14.180+4.19.120-1-1
kmod-mwlwifi - 4.14.180+2019-03-02-31d93860-1
kmod-nf-conntrack - 4.14.180-1
kmod-nf-conntrack6 - 4.14.180-1
kmod-nf-flow - 4.14.180-1
kmod-nf-ipt - 4.14.180-1
kmod-nf-ipt6 - 4.14.180-1
kmod-nf-nat - 4.14.180-1
kmod-nf-reject - 4.14.180-1
kmod-nf-reject6 - 4.14.180-1
kmod-nls-base - 4.14.180-1
kmod-ppp - 4.14.180-1
kmod-pppoe - 4.14.180-1
kmod-pppox - 4.14.180-1
kmod-regmap-core - 4.14.180-1
kmod-scsi-core - 4.14.180-1
kmod-slhc - 4.14.180-1
kmod-usb-core - 4.14.180-1
kmod-usb-ehci - 4.14.180-1
kmod-usb-printer - 4.14.180-1
kmod-usb-storage - 4.14.180-1
kmod-usb2 - 4.14.180-1
kmod-usb3 - 4.14.180-1
**kmod-usbip - 4.14.180-1**
**kmod-usbip-server - 4.14.180-1**
libblkid1 - 2.34-1
libblobmsg-json - 2020-02-27-7da66430-1
libc - 1.1.24-2
libcomerr0 - 1.44.5-2
libevdev - 1.6.0-1
libext2fs2 - 1.44.5-2
libgcc1 - 7.5.0-2
libip4tc2 - 1.8.3-1
libip6tc2 - 1.8.3-1
libiwinfo-lua - 2019-10-16-07315b6f-1
libiwinfo20181126 - 2019-10-16-07315b6f-1
libjson-c2 - 0.12.1-3.1
libjson-script - 2020-02-27-7da66430-1
liblua5.1.5 - 5.1.5-3
liblucihttp-lua - 2019-07-05-a34a17d5-1
liblucihttp0 - 2019-07-05-a34a17d5-1
libnl-tiny - 0.1-5
libopenssl1.1 - 1.1.1g-1
libpopt0 - 1.16-2
libpthread - 1.1.24-2
librt - 1.1.24-2
libss2 - 1.44.5-2
libubox20191228 - 2020-02-27-7da66430-1
libubus-lua - 2019-12-27-041c9d1c-1
libubus20191227 - 2019-12-27-041c9d1c-1
libuci20130104 - 2019-09-01-415f9e48-3
libuclient20160123 - 2019-05-30-3b3e368d-1
**libudev - 3.2-1**
libusb-1.0-0 - 1.0.22-2
libuuid1 - 2.34-1
libwrap - 7.6-2
libxtables12 - 1.8.3-1
logd - 2019-06-16-4df34a4d-3
lua - 5.1.5-3
luci - git-20.136.49537-fb2f363-1
luci-app-advanced-reboot - git-20.155.55664-f35803e-52
luci-app-firewall - git-20.136.49537-fb2f363-1
luci-app-hd-idle - git-20.155.55664-f35803e-1
luci-app-opkg - git-20.136.49537-fb2f363-1
luci-app-p910nd - git-20.155.55664-f35803e-1
luci-base - git-20.136.49537-fb2f363-1
luci-compat - git-20.155.55664-f35803e-1
luci-lib-ip - git-20.136.49537-fb2f363-1
luci-lib-jsonc - git-20.136.49537-fb2f363-1
luci-lib-nixio - git-20.136.49537-fb2f363-1
luci-mod-admin-full - git-20.136.49537-fb2f363-1
luci-mod-network - git-20.136.49537-fb2f363-1
luci-mod-status - git-20.136.49537-fb2f363-1
luci-mod-system - git-20.136.49537-fb2f363-1
luci-proto-ipv6 - git-20.136.49537-fb2f363-1
luci-proto-ppp - git-20.136.49537-fb2f363-1
luci-theme-bootstrap - git-20.136.49537-fb2f363-1
mtd - 24
mwifiex-sdio-firmware - 20190416-1
mwlwifi-firmware-88w8964 - 2019-03-02-31d93860-1
netifd - 2019-08-05-5e02f944-1
odhcp6c - 2019-01-11-e199804b-16
odhcpd-ipv6only - 2020-05-03-49e4949c-3
openssh-sftp-server - 8.0p1-1
openwrt-keyring - 2019-07-25-8080ef34-1
opkg - 2020-05-07-f2166a89-1
p910nd - 0.97-8
ppp - 2.4.7.git-2019-05-25-3
ppp-mod-pppoe - 2.4.7.git-2019-05-25-3
procd - 2020-03-07-09b9bd82-1
rpcd - 2019-12-10-aaa08366-2
rpcd-mod-file - 2019-12-10-aaa08366-2
rpcd-mod-iwinfo - 2019-12-10-aaa08366-2
rpcd-mod-luci - 20191114
rpcd-mod-rrdns - 20170710
rsync - 3.1.3-2
sshpass - 1.06-1
swconfig - 12
ubi-utils - 2.1.1-1
uboot-envtools - 2018.03-3
ubox - 2019-06-16-4df34a4d-3
ubus - 2019-12-27-041c9d1c-1
ubusd - 2019-12-27-041c9d1c-1
uci - 2019-09-01-415f9e48-3
uclient-fetch - 2019-05-30-3b3e368d-1
uhttpd - 2020-03-13-975dce23-1
urandom-seed - 1.0-1
urngd - 2020-01-21-c7f7b6b6-1
**usbip - 2.0-11**
**usbip-server - 2.0-11**
**usbutils - 007-10**
usign - 2019-08-06-5a52b379-1
wireless-regdb - 2019.06.03-1
wpad-basic - 2019-08-08-ca8c2bd2-3
xinetd - 2.3.15-5
zlib - 1.2.11-3
~# usbipd -D
~# usbip list -l
-ash: usbip: not found
~# usbipd -d
usbipd: info: starting usbipd (usbip-utils 2.0)
usbipd: debug: usbipd.c:387:[listen_all_addrinfo] opening 0.0.0.0:3240
usbip: debug: usbip_network.c:261:[usbip_net_set_v6only] setsockopt: IPV6_V6ONLY
usbipd: error: bind: 0.0.0.0:3240: 98 (Address in use)
usbipd: debug: usbipd.c:387:[listen_all_addrinfo] opening :::3240
usbipd: error: bind: :::3240: 98 (Address in use)
usbipd: error: failed to open a listening socket
T4V0
June 9, 2020, 3:46pm
44
You didn't copy the last line to your opkg.conf, which is the one that enables the package installation of the arm_cortex-a9_vfpv3 architecture:
arch arm_cortex-a9_vfpv3 300
Edit:
I misread, your libudev is installed, somehow.
You need usbip-client to use the command:
usbip list -l
But the major problem right is that you can't run the usbip daemon (usbipd -D), try adding the rules to your firewall by running these lines with the proper lan name:
uci add firewall rule
uci set firewall.@rule[-1].name='Allow USBIP'
uci set firewall.@rule[-1].src='lan'
uci set firewall.@rule[-1].dest='lan'
uci set firewall.@rule[-1].proto='tcp'
uci set firewall.@rule[-1].dest_port='3240'
uci set firewall.@rule[-1].target='ACCEPT'
uci commit firewall
service firewall restart
1 Like
Sorry, the mistake was when I copied/past the command from the terminal to the post, the line is in fact in the opkg.conf
~# cat /etc/opkg.conf
dest root /
dest ram /tmp
lists_dir ext /var/opkg-lists
option overlay_root /overlay
option check_signature
arch all 100
arch arm_cortex-a9_vfpv3-d16 200
arch arm_cortex-a9_vfpv3 300
So, I installed it
~# usbip list -l
- busid 1-1 (04f9:0248)
Brother Industries, Ltd : DCP-7055 scanner/printer (04f9:0248)
- busid 3-1 (174c:55aa)
ASMedia Technology Inc. : Name: ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SAT
Firewall
After copy/past all the commands,
~# uci show firewall
....
firewall.@rule[9]=rule
firewall.@rule[9].name='Allow USBIP'
firewall.@rule[9].src='lan'
firewall.@rule[9].dest='lan'
firewall.@rule[9].proto='tcp'
firewall.@rule[9].dest_port='3240'
firewall.@rule[9].target='ACCEPT'
Both source and destination are in the lan.
Unfortunately
~# usbipd -D
~# usbipd -d
usbipd: info: starting usbipd (usbip-utils 2.0)
usbipd: debug: usbipd.c:387:[listen_all_addrinfo] opening 0.0.0.0:3240
usbip: debug: usbip_network.c:261:[usbip_net_set_v6only] setsockopt: IPV6_V6ONLY
usbipd: error: bind: 0.0.0.0:3240: 98 (Address in use)
usbipd: debug: usbipd.c:387:[listen_all_addrinfo] opening :::3240
usbipd: error: bind: :::3240: 98 (Address in use)
usbipd: error: failed to open a listening socket
Same issue.
T4V0
June 9, 2020, 6:27pm
46
Ok, almost there. Can you run the command:
netstat -alpt
And paste the output.
You may already be running the daemon if there's a process named usbipd.
Run the commands, with ROUTER_IP being your router's current ip:
usbip bind -b 1-1
usbip list -r ROUTER_IP
1 Like
~# netstat -alpt
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:3240 0.0.0.0:* LISTEN 3545/usbipd
tcp 0 0 MainRouter.locdom.org:9100 0.0.0.0:* LISTEN 2721/p9100d
tcp 0 0 0.0.0.0:www 0.0.0.0:* LISTEN 2222/uhttpd
tcp 0 0 localhost:domain 0.0.0.0:* LISTEN 3346/dnsmasq
tcp 0 0 MainRouter.locdom.org:domain 0.0.0.0:* LISTEN 3346/dnsmasq
tcp 0 0 192.168.11.2:domain 0.0.0.0:* LISTEN 3346/dnsmasq
tcp 0 0 MainRouter.locdom.org:ssh 0.0.0.0:* LISTEN 2777/dropbear
tcp 0 0 MainRouter.locdom.org:www loja.locdom.org:49836 ESTABLISHED 2222/uhttpd
tcp 0 0 MainRouter.locdom.org:www loja.locdom.org:49844 ESTABLISHED 2222/uhttpd
tcp 0 0 MainRouter.locdom.org:www loja.locdom.org:49834 ESTABLISHED 2222/uhttpd
tcp 0 0 MainRouter.locdom.org:ssh loja.locdom.org:57734 ESTABLISHED 3602/dropbear
tcp 0 0 MainRouter.locdom.org:www loja.locdom.org:49838 ESTABLISHED 2222/uhttpd
tcp 0 0 MainRouter.locdom.org:www loja.locdom.org:49842 ESTABLISHED 2222/uhttpd
tcp 0 160 MainRouter.locdom.org:ssh loja.locdom.org:57608 ESTABLISHED 3480/dropbear
tcp 0 0 MainRouter.locdom.org:ssh loja.locdom.org:57738 ESTABLISHED 3605/dropbear
tcp 0 0 MainRouter.locdom.org:www loja.locdom.org:49840 ESTABLISHED 2222/uhttpd
tcp 0 0 :::3240 :::* LISTEN 3545/usbipd
tcp 0 0 :::www :::* LISTEN 2222/uhttpd
tcp 0 0 fe80::6038:e0ff:fece:8012:domain :::* LISTEN 3346/dnsmasq
tcp 0 0 fe80::6238:e0ff:fece:8013:domain :::* LISTEN 3346/dnsmasq
tcp 0 0 fe80::6038:e0ff:fece:8011:domain :::* LISTEN 3346/dnsmasq
tcp 0 0 localhost:domain :::* LISTEN 3346/dnsmasq
tcp 0 0 fe80::6238:e0ff:fece:8010:domain :::* LISTEN 3346/dnsmasq
tcp 0 0 fe80::6038:e0ff:fece:8010:domain :::* LISTEN 3346/dnsmasq
tcp 0 0 fe80::6038:e0ff:fece:8010:domain :::* LISTEN 3346/dnsmasq
tcp 0 0 fe80::6238:e0ff:fece:8010:domain :::* LISTEN 3346/dnsmasq
Yes, usbipd is here
~# usbip bind -b 1-1
usbip: info: bind device on busid 1-1: complete
~# usbip list -r 192.168.1.1
#Exportable USB devices
======================
- 192.168.1.1
1-1: Brother Industries, Ltd : DCP-7055 scanner/printer (04f9:0248)
: /sys/devices/platform/soc/soc:internal-regs/f1058000.usb/usb1/1-1
: (Defined at Interface level) (00/00/00)
And now?
T4V0
June 9, 2020, 6:53pm
48
Now you can make it run automatically on boot by adding these lines in your /etc/rc.local file, before exit 0:
usbipd -D
sleep 1
usbip bind -b 1-1
Then install usbip on your PC, and run the command, with ROUTER_IP being your router's current ip:
usbip attach -r ROUTER_IP -b 1-1
Afterwards you can install the Brother's scanner driver and run the command, as root, to see if it's detected:
scanimage -L
1 Like
vi /etc/rc.local
...
~# cat /etc/rc.local
# Put your custom commands here that should be executed once
# the system init finished. By default this file does nothing.
usbipd -D
sleep 1
usbip bind -b 1-1
exit 0
Reboot then Scanner connected
~# usbip list -r 192.168.1.1
Exportable USB devices
======================
- 192.168.1.1
1-1: Brother Industries, Ltd : DCP-7055 scanner/printer (04f9:0248)
: /sys/devices/platform/soc/soc:internal-regs/f1058000.usb/usb1/1-1
: (Defined at Interface level) (00/00/00)
~# usbipd -d
usbipd: info: starting usbipd (usbip-utils 2.0)
usbipd: debug: usbipd.c:387:[listen_all_addrinfo] opening 0.0.0.0:3240
usbip: debug: usbip_network.c:261:[usbip_net_set_v6only] setsockopt: IPV6_V6ONLY
usbipd: error: bind: 0.0.0.0:3240: 98 (Address in use)
usbipd: debug: usbipd.c:387:[listen_all_addrinfo] opening :::3240
usbipd: error: bind: :::3240: 98 (Address in use)
usbipd: error: failed to open a listening socket
Error here
Computer:
~> sudo usbip --debug attach -r 192.168.1.1 -b 1-1
usbip: debug: usbip.c:129:[run_command] running command: `attach'
libusbip: error: udev_device_new_from_subsystem_sysname failed
usbip: error: open vhci_driver
T4V0
June 9, 2020, 7:26pm
50
Make sure the PC has the vhci-hcd
module loaded, as root:
modprobe vhci-hcd
1 Like
Not yet, hard time!! Thank you for your patience.
PC:
~> sudo modprobe vhci-hcd
~> lsmod | grep vhci_hcd
vhci_hcd 45056 0
usbip_core 32768 1 vhci_hcd
usbcore 290816 10 usbhid,snd_usb_audio,vhci_hcd,ehci_hcd,ohci_pci,xhci_pci,snd_usbmidi_lib,ohci_hcd,xhci_hcd,ehci_pci
I'd guess I'll have to set it up for activation at boot.
Did you notice error in the router in my previous post?
T4V0
June 9, 2020, 7:54pm
52
That's not an actual error, you are trying to run usbipd twice, if usbipd is running in the background you can't run it again. You would need to kill the process with its pid first and then run usbipd -d
again. But that will run on your current ssh session, so it's best to run usbipd -D
once and let it run in the background.
OK, got it
PC:
~> sudo usbip --debug attach -r 192.168.1.1 -b 1-1
[sudo] password for root:
usbip: debug: usbip.c:129:[run_command] running command: `attach'
libusbip: error: udev_device_new_from_subsystem_sysname failed
usbip: error: open vhci_driver
I can't see libusbip in installed packages, neither in the repo.
T4V0
June 9, 2020, 8:44pm
54
The libusbip is just usbip's library. Can you paste these commands output on the PC:
usbip version
usbip list -r 192.168.1.1
libusbip: error: udev_device_new_from_subsystem_sysname failed
usbip: error: open vhci_driver
Sounds like the vhci-hcd module hasn't been loaded.
~> sudo usbip version
[sudo] password for root:
usbip (usbip-utils 2.0)
~> sudo usbip list -r 192.168.1.1
Exportable USB devices
======================
- 192.168.1.1
1-1: Brother Industries, Ltd : DCP-7055 scanner/printer (04f9:0248)
: /sys/devices/platform/soc/soc:internal-regs/f1058000.usb/usb1/1-1
: (Defined at Interface level) (00/00/00)
~> lsmod
Module Size Used by
vhci_hcd 45056 0
usbip_core 32768 1 vhci_hcd
Should be good, no? I am stuck.
T4V0
June 9, 2020, 9:20pm
56
Try to kill usbipd process in the router and run:
usbipd -d
Then open another terminal window and try connecting again with:
usbip --debug attach -r ROUTER_IP -b 1-1
Router:
kill -15 [usbipd pid]
usbipd not in top
reboot the router
close the terminal
open new terminal and ssh
~# usbipd -d
usbipd: info: starting usbipd (usbip-utils 2.0)
usbipd: debug: usbipd.c:387:[listen_all_addrinfo] opening 0.0.0.0:3240
usbip: debug: usbip_network.c:261:[usbip_net_set_v6only] setsockopt: IPV6_V6ONLY
usbipd: info: listening on 0.0.0.0:3240
usbipd: debug: usbipd.c:387:[listen_all_addrinfo] opening :::3240
usbipd: info: listening on :::3240
usbipd: debug: usbipd.c:542:[do_standalone_mode] listening on 2 addresses
usbipd: debug: usbipd.c:573:[do_standalone_mode] heartbeat timeout on ppoll()
usbipd: debug: usbipd.c:573:[do_standalone_mode] heartbeat timeout on ppoll()
usbipd: debug: usbipd.c:573:[do_standalone_mode] heartbeat timeout on ppoll()
usbipd: debug: usbipd.c:573:[do_standalone_mode] heartbeat timeout on ppoll()
~# usbip --debug attach -r ROUTER_IP -b 1-1
usbip: debug: usbip.c:141:[run_command] running command: `attach'
usbip: debug: usbip_network.c:283:[usbip_net_tcp_connect] getaddrinfo: ROUTER_IP service 3240: Name does not resolve
usbip: error: tcp connect
top: usbipd is not running
but
~# cat /etc/rc.local
# Put your custom commands here that should be executed once
# the system init finished. By default this file does nothing.
usbipd -D
sleep 1
usbip bind -b 1-1
exit 0
~# ps | grep usb
716 root 0 SW [usb-storage]
1483 root 0 IW< [usbip_event]
3337 p910nd 704 S {p910nd} /usr/sbin/p9100d -d -b -f /dev/usb/lp0 -i 192.168.1.1 0
4180 root 1072 R grep usb
?
nota: It's late, thank you a million. See you tomorrow
T4V0
June 9, 2020, 9:52pm
58
Sorry, forgot to mention that should've been the router's ip address. But you can run this instead:
sudo usbip --debug attach -r openwrt -b 1-1
No problem, see you.
Of course! I was tired yesterday evening!
So, now usbipd -D is running (checked with top)
From router:
~# usbip list -l
- busid 1-1 (04f9:0248)
Brother Industries, Ltd : DCP-7055 scanner/printer (04f9:0248)
- busid 3-1 (174c:55aa)
ASMedia Technology Inc. : Name: ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SAT
~# usbip --debug attach -r 192.168.1.1 -b 1-1
usbip: debug: usbip.c:141:[run_command] running command: `attach'
usbip: debug: usbip_network.c:207:[usbip_net_recv_op_common] request failed at peer: 1
usbip: error: recv op_common
usbip: error: query
I understand that this error need to be fixed before working on the client side.
I found a link about usbip here then below, click on "Readme for Linux".
T4V0
June 10, 2020, 6:08pm
60
Looking at the openwrt usbip guide it seems I missed a kmod package installation:
opkg install kmod-usb-ohci
Is the device binded? usbip bind -b 1-1
If it's already binded, unbind it, kill the usbipd process, restart it and bind again:
usbip unbind -b 1-1
killall usbipd
usbipd -D
usbip bind -b 1-1
usbip --debug attach -r 192.168.1.1 -b 1-1
Following the instructions:
~# usbip unbind -b 1-1
usbip: error: device is not bound to usbip-host driver
~# killall usbipd
~# usbipd -D
~# usbip bind -b 1-1
usbip: info: bind device on busid 1-1: complete
~# usbip --debug attach -r 192.168.1.1 -b 1-1
usbip: debug: usbip.c:141:[run_command] running command: `attach'
libusbip: debug: vhci_driver.c:269:[usbip_vhci_driver_open] available ports: 16
libusbip: debug: vhci_driver.c:281:[usbip_vhci_driver_open] available controllers: 1
libusbip: debug: vhci_driver.c:128:[refresh_imported_device_list] controller 0
libusbip: debug: vhci_driver.c:68:[parse_status] hub hs port 0 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0
libusbip: debug: vhci_driver.c:68:[parse_status] hub hs port 1 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0
libusbip: debug: vhci_driver.c:68:[parse_status] hub hs port 2 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0
libusbip: debug: vhci_driver.c:68:[parse_status] hub hs port 3 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0
libusbip: debug: vhci_driver.c:68:[parse_status] hub hs port 4 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0
libusbip: debug: vhci_driver.c:68:[parse_status] hub hs port 5 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0
libusbip: debug: vhci_driver.c:68:[parse_status] hub hs port 6 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0
libusbip: debug: vhci_driver.c:68:[parse_status] hub hs port 7 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0
libusbip: debug: vhci_driver.c:68:[parse_status] hub ss port 8 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0
libusbip: debug: vhci_driver.c:68:[parse_status] hub ss port 9 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0
libusbip: debug: vhci_driver.c:68:[parse_status] hub ss port 10 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0
libusbip: debug: vhci_driver.c:68:[parse_status] hub ss port 11 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0
libusbip: debug: vhci_driver.c:68:[parse_status] hub ss port 12 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0
libusbip: debug: vhci_driver.c:68:[parse_status] hub ss port 13 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0
libusbip: debug: vhci_driver.c:68:[parse_status] hub ss port 14 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0
libusbip: debug: vhci_driver.c:68:[parse_status] hub ss port 15 status 4 speed 0 devid 0
libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0
libusbip: debug: vhci_driver.c:104:[parse_status] exit
usbip: debug: usbip_attach.c:112:[import_device] got free port 0
libusbip: debug: vhci_driver.c:367:[usbip_vhci_attach_device2] writing: 0 3 65538 3
libusbip: debug: vhci_driver.c:372:[usbip_vhci_attach_device2] attach attribute path: /sys/devices/platform/vhci_hcd.0/attach
libusbip: debug: vhci_driver.c:380:[usbip_vhci_attach_device2] attached port: 0
Looks like it is attached
Client side (PC):
~> sudo usbip list -r 192.168.1.1
Exportable USB devices
======================
- 192.168.1.1
1-1: Brother Industries, Ltd : DCP-7055 scanner/printer (04f9:0248)
: /sys/devices/platform/soc/soc:internal-regs/f1058000.usb/usb1/1-1
: (Defined at Interface level) (00/00/00)
: 0 - Printer / Printer / Bidirectional (07/01/02)
: 1 - Vendor Specific Class / Vendor Specific Subclass / Vendor Specific Protocol (ff/ff/ff)
~> sudo usbip attach -r 192.168.1.1 -b 1-1
[sudo] password for root:
usbip: error: Attach Request for 1-1 failed - Request Failed
~> lsmod | grep vhci
~>
~> sudo modprobe vhci-hcd
jp@loja:~> lsmod | grep vhci
vhci_hcd 45056 0
usbip_core 32768 1 vhci_hcd
usbcore 290816 10 usbhid,snd_usb_audio,vhci_hcd,ehci_hcd,ohci_pci,xhci_pci,snd_usbmidi_lib,ohci_hcd,xhci_hcd,ehci_pci
~> sudo usbip attach -r 192.168.1.1 -b 1-1
usbip: error: Attach Request for 1-1 failed - Request Failed
No idea what to do now
T4V0
June 10, 2020, 6:59pm
62
You need to detach on the router first.
Router:
sudo usbip detach -p 0
PC:
sudo usbip attach -r openwrt -b 1-1