br14:
usb 1-1: USB disconnect, device number **58**
Fri Jan 17 15:17:19 2025 kern.info kernel: [15856.521617] rndis_host 1-1:1.0 eth1: unregister 'rndis_host' usb-1b000000.usb-1, RNDIS device
Fri Jan 17 15:17:20 2025 kern.info kernel: [15857.080635] usb 1-1: new high-speed USB device number **59** using ehci-platform
Fri Jan 17 15:17:24 2025 kern.info kernel: [15861.251902] usb 1-1: USB disconnect, device number **59**
Fri Jan 17 15:17:24 2025 kern.info kernel: [15861.810944] usb 1-1: new high-speed USB device number **60** using ehci-platform
Fri Jan 17 15:17:25 2025 kern.info kernel: [15862.017956] rndis_host 1-1:1.0 eth1: register 'rndis_host' at usb-1b000000.usb-1, RNDIS device, 0e:e2:40:87:cb:7f
...
---> Install kmod-usb-net-cdc-ncm
17 15:21:00 2025 user.info kernel: [16077.144921] kmodloader: loading kernel modules from /etc/modules.d/*
Fri Jan 17 15:21:00 2025 kern.info kernel: [16077.168219] usbcore: registered new interface driver cdc_ncm
Fri Jan 17 15:21:00 2025 user.info kernel: [16077.176762] kmodloader: done loading kernel modules from /etc/modules.d/*
...
---> Turn off and then turn on USB-tethering on the phone
17 15:22:50 2025 kern.info kernel: [16187.271784] usb 1-1: USB disconnect, device number **60**
Fri Jan 17 15:22:50 2025 kern.info kernel: [16187.277137] rndis_host 1-1:1.0 eth1: unregister 'rndis_host' usb-1b000000.usb-1, RNDIS device
Fri Jan 17 15:22:51 2025 kern.info kernel: [16187.853671] usb 1-1: new high-speed USB device number **61** using ehci-platform
Fri Jan 17 15:22:52 2025 kern.info kernel: [16189.468031] usb 1-1: USB disconnect, device number **61**
Fri Jan 17 15:22:53 2025 kern.info kernel: [16190.033830] usb 1-1: new high-speed USB device number **62** using ehci-platform
Fri Jan 17 15:22:53 2025 kern.info kernel: [16190.241107] rndis_host 1-1:1.0 eth1: register 'rndis_host' at usb-1b000000.usb-1, RNDIS device, 0e:e2:40:87:cb:7f
I was afraid of something like this:
It is creating a new USB device every time; that log shows the 58th-62nd device.
Same device but it is not being properly handled by the overload of unnecessary USB packages.
...or so I see it.
mk24
January 17, 2025, 9:11pm
22
In both logs that the OP posted, the virtual Ethernet port enumerated as eth1. Attach the wan network to that name. I'm going to assume the kernel driver has been changed so that names of the form usbN are no longer used.
br14
January 17, 2025, 9:59pm
23
Solved. AndrewZ was right, the device indeed is eth1
and it's there when everything is properly turned on at the right time. User error. Now I'll have to see how stable this USB-tethering connection will be.
Thanks to everyone who responded.
system
Closed
January 27, 2025, 9:59pm
24
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.