Chili.Willy

Update: Since the previous post, usbip has been upgraded on the client (Debian Bullseye laptop) but not on the Raspberry Pi Raspbian Bullseye server. There's one new thing. When I issue this command on the R. Pi server: sudo usbip list -r 127.0.0.1 telling it to look for bound devices, it prints the following line: usbip: error: Protocol spec without prior Class and Subclass spec at line 23299 and then it prints the CORRECT output, showing the Brother all-in-one inkjet. When I issue, on the client...

Update. No progress, but I have new information. usbip has been updated in both the Raspberry Pi server and the Debian Bullseye client: usbip-utils 2.0. When I bind my all-in-one printer to the R. Pi server with sudo usbip bind -b 1-1.3.2, then I can start usbipd with the debug option, usbipd -d. This output results: usbipd: info: starting usbipd (usbip-utils 2.0) usbipd: debug: usbipd.c:389:[listen_all_addrinfo] opening 0.0.0.0:3240 usbip: debug: usbip_network.c:253:[usbip_net_set_v6only] setsockopt:...

I've been using usbip to scan for a long time. The server is a Raspberry Pi, a Model B I think (old!) with Raspbian Bullseye. The client is a laptop running Debian 11 Bullseye. It may have been when I updated the client from 10 Buster to 11 Bullseye that usbip stopped working. (I had updated the Pi a few months earlier.) lsmod on the R. Pi server shows that usbip_host, usbip_core, and configs are loaded. usbip list -l shows 3 devices including the Brother all-in-one that includes the scanner. When...