Post History
I was looking through the unpacked file that I find in /proc/config.gz on the host system. There was: # CONFIG_USB_NET_DRIVERS is not set What I also found is that, the host side counterpart to t...
Answer
#1: Initial revision
I was looking through the unpacked file that I find in /proc/config.gz on the host system. There was: _# CONFIG_USB_NET_DRIVERS is not set_ What I also found is that, the host side counterpart to the gadget device's _g_ether_ driver, is supposedly the _cdc_ether_ driver. I found mentions of _CONFIG_USB_NET_CDCETHER_ , _CONFIG_USB_USBNET_ and other USB_NET options that supposedly need to be onm in other posts elsewhere. My config file does not contain that text except for the mentioned CONFIG_USB_NET_DRIVERS - but apparently, dependant options of a main option are not always also put into the config text file. Generating a new kernel image, with the following items added to the kernel configuration, helped, and I now get a "usb0" interface shown under _ifconfig -a_ : * CONFIG_USB_NET_DRIVERS * CONFIG_USB_USBNET * CONFIG_USB_NET_CDCETHER * CONFIG_USB_NET_CDC_EEM next to options generally enabling USB and enable it as a host (or dual role). I'm not sure whether the last one is necessary, haven't tried. [Its description](https://cateee.net/lkddb/web-lkddb/USB_NET_CDC_EEM.html) sounded like it could be relevant, as it mentions a _usbX_ interface name, which I knew from the Raspi4-as-host experiment.