Ethernet port in an USB-C dock - failure to attach to sys-net

[Kristian Elof Sørensen]

Hello

I'm trying to make a Gigabit Ethernet port in an USB-C dock available to sys-net

How come this does not work? My mistake or hardware not fully supported by kernel/qubes?

Qubes 3.2
Linux kernel 4.9.56-21
Asus SimPro Dock https://www.asus.com/Docks/ASUS-SimPro-Dock/specifications/

[user@sys-usb ~]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 005: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
............

[username@dom0 ~]$ qvm-usb 
sys-usb:3-1.2.4 0b95:1790 ASIX_Elec._Corp._AX88179_00000000000001
sys-usb:2-1.3 1fc9:500d NXP_SIMPRODOCK_PD_2.100_0000098e0695
sys-usb:2-1.2.3 0bda:4040 Generic_USB_Audio_201405280001
sys-usb:2-8 8087:0a2b 8087_0a2b

[username@dom0 ~]$ qvm-usb -a sys-net sys-usb:3-1.2.4
ERROR: Device attach failed: /usr/lib/qubes/usb-import: line 37: [: sta: integer expression expected/usr/lib/qubes/usb-import: line 51: printf: write error: Invalid argument

[Yethal]

You shouldn't have to do that, sys-usb is a NetVM by default.

[Kristian Elof Sørensen]

> You shouldn't have to do that, sys-usb is a NetVM by default.
>

Interesting.

the sys-usb is indeed listes as "Type: NetVM"

However the ethernet device does not show up when running ifconfig or the "Network Connections" gui program.

When plugging in the USB-C dock, I see this:

[user@sys-usb ~]$ sudo dmesg -w
.......
[22271.385720] usb 3-1.2.4: new SuperSpeed USB device number 9 using xhci_hcd
[22271.404341] usb 3-1.2.4: New USB device found, idVendor=0b95, idProduct=1790
[22271.404371] usb 3-1.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[22271.404389] usb 3-1.2.4: Product: AX88179
[22271.404401] usb 3-1.2.4: Manufacturer: ASIX Elec. Corp.
[22271.404412] usb 3-1.2.4: SerialNumber: 00000000000001
[22271.739817] ax88179_178a 3-1.2.4:1.0 eth0: register 'ax88179_178a' at usb-0000:00:00.0-1.2.4, ASIX AX88179 USB 3.0 Gigabit Ethernet, 60:45:cb:bd:16:c8
[22271.803545] ax88179_178a 3-1.2.4:1.0 enp0s0f0u1u2u4: renamed from eth0

[user@sys-usb ~]$ /sbin/ifconfig 
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 36  bytes 2016 (1.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 36  bytes 2016 (1.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

No other network device than "lo" is listed? I would have expected either eth0 or enp0s0f0u1u2u4 ?

Kristian

[Yethal]

what does lsusb in sys-usb show? What's the listed device class?

[Kristian Elof Sørensen]

> what does lsusb in sys-usb show? What's the listed device class?

[user@sys-usb ~]$ lsusb -s 003:013 -v

Bus 003 Device 013: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit
Ethernet
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               3.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol         0 
  bMaxPacketSize0         9
  idVendor           0x0b95 ASIX Electronics Corp.
  idProduct          0x1790 AX88179 Gigabit Ethernet
  bcdDevice            1.00
  iManufacturer           1 
  iProduct                2 
  iSerial                 3 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           57
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol      0 
      iInterface              4 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              11
        bMaxBurst               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst               3
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst              15

[Yethal]

Device class is listed as vendor specific class (and not a usb ethernet device) so you'll need to manually tell qubes to use that device as a network interface.

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sun, Dec 17, 2017 at 09:08:29PM +0100, Kristian Elof Sørensen wrote:
>
> > You shouldn't have to do that, sys-usb is a NetVM by default.
> >
>
> Interesting.
>
> the sys-usb is indeed listes as "Type: NetVM"
>
> However the ethernet device does not show up when running ifconfig or the "Network Connections" gui program.

By default network manager is disabled in sys-usb, to avoid confusion
(two identical icons). You can enable it in "services" tab of sys-usb
settings.

> When plugging in the USB-C dock, I see this:
>
> [user@sys-usb ~]$ sudo dmesg -w
> .......
> [22271.385720] usb 3-1.2.4: new SuperSpeed USB device number 9 using xhci_hcd
> [22271.404341] usb 3-1.2.4: New USB device found, idVendor=0b95, idProduct=1790
> [22271.404371] usb 3-1.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [22271.404389] usb 3-1.2.4: Product: AX88179
> [22271.404401] usb 3-1.2.4: Manufacturer: ASIX Elec. Corp.
> [22271.404412] usb 3-1.2.4: SerialNumber: 00000000000001
> [22271.739817] ax88179_178a 3-1.2.4:1.0 eth0: register 'ax88179_178a' at usb-0000:00:00.0-1.2.4, ASIX AX88179 USB 3.0 Gigabit Ethernet, 60:45:cb:bd:16:c8
> [22271.803545] ax88179_178a 3-1.2.4:1.0 enp0s0f0u1u2u4: renamed from eth0
>
> [user@sys-usb ~]$ /sbin/ifconfig 
> lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
>         inet 127.0.0.1  netmask 255.0.0.0
>         inet6 ::1  prefixlen 128  scopeid 0x10<host>
>         loop  txqueuelen 1  (Local Loopback)
>         RX packets 36  bytes 2016 (1.9 KiB)
>         RX errors 0  dropped 0  overruns 0  frame 0
>         TX packets 36  bytes 2016 (1.9 KiB)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> No other network device than "lo" is listed? I would have expected either eth0 or enp0s0f0u1u2u4 ?

Check ifconfig -a

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlo66Q4ACgkQ24/THMrX
1yxOOgf/fEeHmZcvzBBph/QMKt5TE/eEgbY4xlteXS62GQw3ib3pRqpQRpkjFZxF
kNh2l+990y20Jptc+swpgyDdQyNUPzLbuwNMXPm78YhbrVuaDT6x2/lz/zSSusj+
PyC5R6+vQgmK9y0yJpO1If24IAI0aELykEbeSUXgWIRSRyX/lQlmkNOjtYlHGT2S
nA+5vFk3rhOd4oQhPGKI90o4pWG40sGtB8CuFSiRYF1YNr9LVYCMi8nGyamJl63U
z9gbYM5Tbp6RGWmiRzyU+EuZULiYPEAHl5xIJp3vEbHF0lIsH828Gk1q1SwCmVZ8
VcjMkaOXB5D490Q4f/maeMhgSCBIgw==
=i34j
-----END PGP SIGNATURE-----