On the second side, the interface name is enp0s29u1u1u4. On the first side, the output doesn't make sense, I would try again.
BUT, of interest, it looks like the hardware in the middle of the cable turns out to be two Prolific USB-to-serial adapters back to back in Ethernet Emulator mode... So, while this WILL work, it was also suggested already, and failed the "Not ethernet" requirement in the original problem statement... On Tue, Jun 19, 2018, 08:16 Richard Owlett <[email protected]> wrote: > Plug in one end of cable > [ 1882.167155] usb 4-1.1.4: new high-speed USB device number 4 using > ehci-pci > [ 1882.278177] usb 4-1.1.4: New USB device found, idVendor=067b, > idProduct=25a1 > [ 1882.278183] usb 4-1.1.4: New USB device strings: Mfr=1, Product=2, > SerialNumber=0 > [ 1882.278187] usb 4-1.1.4: Product: USB Transfer Cable > [ 1882.278191] usb 4-1.1.4: Manufacturer: Prolific Technology Inc. > [ 1882.301597] plusb 4-1.1.4:1.0 usb0: register 'plusb' at > usb-0000:00:1d.0-1.1.4, Prolific PL-2301/PL-2302/PL-25A1/PL-27A1, > 1e:1c:40:06:14:68 > [ 1882.301642] usbcore: registered new interface driver plusb > [ 1882.306204] plusb 4-1.1.4:1.0 enp0s29u1u1u4: renamed from usb0 > [ 1882.333434] IPv6: ADDRCONF(NETDEV_UP): enp0s29u1u1u4: link is not ready > > > Plug in other end of cable also > [ 1887.342562] plusb 4-1.1.4:1.0 enp0s29u1u1u4: kevent 12 may have been > dropped > [ 1887.342580] plusb 4-1.1.4:1.0 enp0s29u1u1u4: kevent 12 may have been > dropped > [ 1887.344176] plusb 4-1.1.4:1.0 enp0s29u1u1u4: kevent 12 may have been > dropped > [ 1887.344197] plusb 4-1.1.4:1.0 enp0s29u1u1u4: kevent 12 may have been > dropped > [ 1906.022817] usb 4-1.1.3: new high-speed USB device number 5 using > ehci-pci > [ 1906.133374] usb 4-1.1.3: New USB device found, idVendor=067b, > idProduct=25a1 > [ 1906.133381] usb 4-1.1.3: New USB device strings: Mfr=1, Product=2, > SerialNumber=0 > [ 1906.133385] usb 4-1.1.3: Product: USB Transfer Cable > [ 1906.133389] usb 4-1.1.3: Manufacturer: Prolific Technology Inc. > [ 1906.134334] plusb 4-1.1.3:1.0 usb0: register 'plusb' at > usb-0000:00:1d.0-1.1.3, Prolific PL-2301/PL-2302/PL-25A1/PL-27A1, > 1e:1c:40:06:14:68 > [ 1906.152962] plusb 4-1.1.3:1.0 enp0s29u1u1u3: renamed from usb0 > [ 1906.185788] IPv6: ADDRCONF(NETDEV_UP): enp0s29u1u1u3: link is not ready > [ 1911.405952] plusb 4-1.1.3:1.0 enp0s29u1u1u3: kevent 12 may have been > dropped > [ 1911.405966] plusb 4-1.1.3:1.0 enp0s29u1u1u3: kevent 12 may have been > dropped > [ 1911.407590] plusb 4-1.1.3:1.0 enp0s29u1u1u3: kevent 12 may have been > dropped > [ 1911.407614] plusb 4-1.1.3:1.0 enp0s29u1u1u3: kevent 12 may have been > dropped > root@debian-jan13:/home/richard# > > > > > On 06/19/2018 08:12 AM, Russell Senior wrote: > > Just as an example of something remotely like what you might expect to > see > > in the dmesg output, here's what I see when I plug a usb-ethernet adapter > > into a Ubuntu 16.04 USB 3 port: > > > > [...] > > [2793539.351788] usb 3-2: new SuperSpeed USB device number 2 using > xhci_hcd > > [2793539.378837] usb 3-2: New USB device found, idVendor=0b95, > > idProduct=1790 > > [2793539.378846] usb 3-2: New USB device strings: Mfr=1, Product=2, > > SerialNumber=3 > > [2793539.378851] usb 3-2: Product: AX88179 > > [2793539.378856] usb 3-2: Manufacturer: ASIX Elec. Corp. > > [2793539.378861] usb 3-2: SerialNumber: 000050B61F4505 > > [2793540.800220] ax88179_178a 3-2:1.0 eth0: register 'ax88179_178a' at > > usb-0000:00:14.0-2, ASIX AX88179 USB 3.0 Gigabit Ethernet, > 00:50:b6:1f:45:05 > > [2793540.801218] usbcore: registered new interface driver ax88179_178a > > [2793540.842186] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready > > [2793541.169959] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready > > > > The link is not ready because I haven't connected an ethernet cable to > the > > adapter, nor an active device to the other end of the ethernet cable. > > Note, in my case I see the ethernet interface is named eth0. Your mileage > > may vary. > > > > On Tue, Jun 19, 2018 at 5:27 AM, Russell Senior < > [email protected]> > > wrote: > > > >> So, do you see the usbN interface or not? > >> > >> On Tue, Jun 19, 2018 at 5:12 AM, Richard Owlett <[email protected]> > >> wrote: > >> > >>> On 06/19/2018 06:45 AM, Russell Senior wrote: > >>> > >>>> Here is someone 10 years ago, using debian: > >>>> > >>>> > >>>> https://jonmccune.wordpress.com/2008/12/09/prolific-pl-25a1- > >>>> usb-to-usb-bridge-in-linux/ > >>>> > >>> > >>> Now bookmarked. I read. It stated in part "... a new usbX network > >>> interface (view with `ifconfig -a`)." > >>> I tried and was given much - need to read up to understand what it > tells > >>> me. > >>> > >>> Then I read the rest of your post ;/ > >>> > >>> > >>> > >>>> What your distribution does (even if it is still Debian) might be > >>>> different > >>>> today, but it looks like it creates a network interface (usbN, in this > >>>> case). Again, your mileage might vary, but the dmesg output should > tell > >>>> you what interface name is assigned. > >>>> > >>>> You could also compare the output before and after plugging in the > cable > >>>> of > >>>> the command: ip addr > >>>> > >>>> For example: > >>>> > >>>> ip addr > /tmp/before-plugging.txt > >>>> [plug in device] > >>>> ip addr > /tmp/after-plugging.txt > >>>> diff -u /tmp/before-plugging.txt /tmp/after-plugging.txt > >>>> > >>>> The difference should be the newly created network interface. > >>>> > >>> > >>> _______________________________________________ > >>> PLUG mailing list > >>> [email protected] > >>> http://lists.pdxlinux.org/mailman/listinfo/plug > >>> > >> > >> > > _______________________________________________ > > PLUG mailing list > > [email protected] > > http://lists.pdxlinux.org/mailman/listinfo/plug > > > > > > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
