Сетевой драйвер usb linux

How to use USB device networking

The Linux USB gadget sub-system supports USB device functionality, including USB networking.

Contents

• 1 Configure hardware for USB OTG or USB device support
• 2 Build USB Ethernet network gadget driver
• 3 Load USB Ethernet network gadget driver
• 4 Connect device to host PC
• 5 Assigning IP addresses
• 6 Verifying network connectivity
• 7 Bridging host PC to allow device to reach the Internet
• 8 Configuring a DNS name server
• 9 Mounting NFS file system
• 10 Debugging and resolving common errors
  • 10.1 Wireshark
  • 10.2 NFS mount failed reason given by server: Permission denied

  Configure hardware for USB OTG or USB device support

  Depending on your hardware, you can use either USB OTG or USB device to enable support for USB networking.

  Build USB Ethernet network gadget driver

  The USB Ethernet network gadget driver caused the device to appear to be a USB network dongle when connected to a host computer. Generally it is best to build USB gadget drivers as modules instead of building them into the kernel so you can unload one and load another.

  Symbol: USB_ETH [=m] Prompt: Ethernet Gadget (with CDC Ethernet support) Defined at drivers/usb/gadget/Kconfig:628 Depends on: && NET Location: -> Kernel configuration -> Device Drivers -> USB support (USB_SUPPORT [=y]) -> USB Gadget Support (USB_GADGET [=y]) -> USB Gadget Drivers ( [=m])

  If you want the target to mount a host PC directory using NFS, then also enable NFS mount support in busybox:

  Symbol: FEATURE_MOUNT_NFS [=n] Prompt: Support mounting NFS file systems Defined at util-linux/Config.in:549 Depends on: FS_APPS_BUSYBOX && MOUNT Location: -> File System Configuration -> Select target's file system software -> busybox-1.18.2 (FS_APPS_BUSYBOX [=y]) -> Busybox configuration -> Linux System Utilities -> mount (MOUNT [=y]) Selects: FEATURE_HAVE_RPC && FEATURE_SYSLOG

  Build the SDK and install the new images to the target hardware.

  Load USB Ethernet network gadget driver

  After booting the target hardware to a shell prompt, run:

  and you should see output similar to:

  g_ether gadget: using random self ethernet address g_ether gadget: using random host ethernet address usb0: MAC be:b5:85:ef:48:33 usb0: HOST MAC 1a:b2:c3:43:8a:6e g_ether gadget: Ethernet Gadget, version: Memorial Day 2008 g_ether gadget: g_ether ready

  You can then verify the usb0 network interface exists:

  usb0 Link encap:Ethernet HWaddr BE:B5:85:EF:48:33 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

  Connect device to host PC

  Before connecting the target device to the host PC, watch the syslog, by running the following command on the host PC:

  sudo tail -f /var/log/messages

  Connect the USB cable between the target device and the host PC. The messages file on the host PC should indicate the new USB device was detected.

  Jun 6 10:15:29 contra-lx kernel: [1638241.377831] usb 1-4.4.2: new high speed USB device using ehci_hcd and address 47 Jun 6 10:15:29 contra-lx kernel: [1638241.510787] cdc_subset: probe of 1-4.4.2:1.0 failed with error -22 Jun 6 10:15:29 contra-lx kernel: [1638241.513437] cdc_subset 1-4.4.2:1.1: usb0: register 'cdc_subset' at usb-0000:00:02.1-4.4.2, Linux Device, 82:13:56:20:b4:cb Jun 6 10:15:29 contra-lx kernel: [1638241.513490] usbcore: registered new interface driver cdc_subset Jun 6 10:15:29 contra-lx kernel: [1638241.533442] cdc_ether: probe of 1-4.4.2:1.0 failed with error -16 Jun 6 10:15:29 contra-lx kernel: [1638241.533619] usbcore: registered new interface driver cdc_ether

  On the host you can verify the new usb0 interface exists by running:

  with the output being similar to:

  usb0 Link encap:Ethernet HWaddr 82:13:56:20:b4:cb inet6 addr: fe80::8013:56ff:fe20:b4cb/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:1 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:78 (78.0 B)

  When you connect the cable, in the target device console, you should see:

  g_ether gadget: high speed config #1: CDC Ethernet (ECM)

  Assigning IP addresses

  For this simple example, fixed IP addresses are assigned to the both the host PC USB network interface and the target device USB network interface.

  HOST_USB_IP=10.0.1.1 sudo ifconfig usb0 $HOST_USB_IP netmask 255.255.255.0 route

  with an entry from the route output that looks like

  Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.1.0 * 255.255.255.0 U 0 0 0 usb0 . link-local * 255.255.0.0 U 1000 0 0 eth0 default gw 0.0.0.0 UG 100 0 0 eth0

  HOST_USB_IP=10.0.1.1 TARGET_USB_IP=10.0.1.2 ifconfig usb0 $TARGET_USB_IP netmask 255.255.255.0 route add default gw $HOST_USB_IP route

  with the route showing the default gateway is using usb0

  Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.1.0 * 255.255.255.0 U 0 0 0 usb0 default 10.0.1.1 0.0.0.0 UG 0 0 0 usb0

  Verifying network connectivity

  On the target device, ping the host PC:

  On the host PC, verify the number of packet sent and received is not zero

  Look at the values of RX packets: and TX packets:.

  Bridging host PC to allow device to reach the Internet

  If your host PC is connected to the Internet (through WiFi or Ethernet), then you can allow the target device to share the host PC’s Internet connection. The following shows how to enable, test, and disable. It only works if your host PC doesn’t have a firewall enable. There is a lot of information on how the Internet giving more detailed explanation.

  echo 1 | sudo tee /proc/sys/net/ipv4/ip_forward > /dev/null sudo iptables -P FORWARD ACCEPT sudo iptables -A POSTROUTING -t nat -j MASQUERADE -s 10.0.1.0/24

  And then for reasons I don’t fully undestand, I had to configure usb0 on the host again:

  HOST_USB_IP=10.0.1.1 sudo ifconfig usb0 $HOST_USB_IP netmask 255.255.255.0 route

  ping -c 5 8.8.8.8 # This is Google's domain name server

  To disable forwarding network packets on your host PC:

  echo 0 | sudo tee /proc/sys/net/ipv4/ip_forward > /dev/null sudo iptables -t nat -F POSTROUTING

  Configuring a DNS name server

  If you need to resolve DNS names, you can configure your target hardware to use Google’s DNS server via:

  echo "nameserver 8.8.8.8" >> /etc/resolv.conf

  and you can test that names get resolved by pinging some computer on the Internet:

  Mounting NFS file system

  If you have already enabled NFS share of your development directory target file system, $DEVDIR/fs/fs, then you can easily mount the file system on the target. This is different than a root NFS mount. With a root NFS mount, networking has to be available when the kernel is booting. With a normal (non root file system) NFS mount, you are simply mounting a shared directory somewhere in the target device’s file system.

  First verify you build the target file system kernel with NFS enabled:

  fgrep nfs /proc/filesystems

  Mount host file system on target:

  HOST_USB_IP=10.0.1.1 HOST_NFS_SHARE_DIR=/local/home/tfischer/work/sdk/fs/fs mkdir /tmp/nfs mount -t nfs -n -o nolock,rsize=1024,wsize=1024 $HOST_USB_IP:$HOST_NFS_SHARE_DIR /tmp/nfs

  Debugging and resolving common errors

  Wireshark

  Wireshark is your friend. Run wireshark on your host PC monitoring the usb0 interface and you don’t need any packet filters. If something isn’t working, you will see the last packet that was sent and not responded to. That will give you a big hint as to where to start looking for the problem.

  sudo apt-get install wireshark sudo wireshark -k -i usb0 &

  NFS mount failed reason given by server: Permission denied

  If you see a message like

  mount: 10.0.1.1:/local/home/tfischer/work/sdk/fs/fs failed, reason given by server: Permission denied mount: mounting 10.0.1.1:/local/home/tfischer/work/sdk/fs/fs on /tmp/nfs failed: Bad file descriptor

  and you know you have root NFS working, the cause is due to a different sub-LAN address being used. On your host PC, you need to make sure the 10.0.1.* sub-LAN is exported. Run the following commands to export you home directory to all computers on this sub-LAN:

  echo "$HOME 10.0.1.0/24 (rw,no_root_squash,no_subtree_check)" | sudo tee -a /etc/exports > /dev/null sudo exportfs -a

  Источник

  Ubuntu 17.04. install driver for USB Ethernet Adapter [closed]

  This describes a problem that can’t be reproduced that seemingly went away on its own or was only relevant to a very specific period of time. It’s off-topic as it’s unlikely to help future readers.

  Need to install a USB Ethernet Adapter (lsusb string below) Bus 003 Device 005: ID 0bda:8152 Realtek Semiconductor Corp. I have got four files by the manufacturer: /home/sergey/Downloads/RTL8152/LINUX Andriod/50-usb-realtek-net.rules /home/sergey/Downloads/RTL8152/LINUX Andriod/compatibility.h /home/sergey/Downloads/RTL8152/LINUX Andriod/Makefile /home/sergey/Downloads/RTL8152/LINUX Andriod/r8152.c Q1: Do I need to install these files above somehow? Q2: If Q1 is negative, How to check the Adapter / make it work? Note: The main goal is to connect a Wi-Fi hub (Zyxell KEENETIC) via the above Adapter. Indication on the hub shows no network connection via the Adapter. Please advise. SK EDIT for @chili555 TY for your prompt answer. Pls see the findings below.

  sergey@home-X200CA:~$ lsmod | grep r8152 r8152 49152 0 mii 16384 2 usbnet,r8152 sergey@home-X200CA:~$ ifconfig enp3s0: flags=4163 mtu 1500 inet6 fe80::da50:e6ff:fe9e:f905 prefixlen 64 scopeid 0x20 ether d8:50:e6:9e:f9:05 txqueuelen 1000 (Ethernet) RX packets 618782 bytes 742610979 (742.6 MB) RX errors 0 dropped 1787 overruns 0 frame 0 TX packets 441907 bytes 64009887 (64.0 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 19 enx00e04c362984: flags=4099 mtu 1500 ether 00:e0:4c:36:29:84 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 6098 bytes 2693946 (2.6 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 6098 bytes 2693946 (2.6 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ppp0: flags=4305 mtu 1492 inet 5.35.51.212 netmask 255.255.255.255 destination 5.35.0.1 ppp txqueuelen 3 (Point-to-Point Protocol) RX packets 458293 bytes 537885941 (537.8 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 337967 bytes 41480878 (41.4 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sergey@home-X200CA:~$ dmesg | grep r8152 [ 16.811429] usbcore: registered new interface driver r8152 [ 17.019410] r8152 3-1.3:1.0 eth0: v1.08.8 [ 19.889560] r8152 3-1.3:1.0 enx00e04c362984: renamed from eth0 sergey@home-X200CA:~$ dmesg | grep inp350 sergey@home-X200CA:~$ sergey@home-X200CA:~$ dmesg | grep inp3s0 sergey@home-X200CA:~$ 

  Источник

  Установка драйвера USB WiFi адаптера в Linux (на примере DEXP WFA-601)

  В связи с переездом и нежеланием захламлять дом проводами повесил в прихожей роутер, а для компьютера купил Wi-Fi адаптер DEXP WFA-601.
  Пока работал в Windows 10 проблем не было. Однако сгоревший жесткий диск подтолкнул меня к установке Linux (конкретно Kubuntu).

  Путь веры

  Захожу на официальный сайт производителя и скачиваю драйвер для любой ОС. Результат предсказуем: Linux != «любая ОС».
  Роюсь в коробочках и нахожу родной CD-диск от адаптера. Скачиваю драйвер, нахожу «install.sh»:

  $ chmod a+x install.sh $ sudo ./install.sh 

  Драйвер не компилируется, вылетает с ошибкой.

  cc1: error: code model kernel does not support PIC mode

  Не буду тратить время на описание, боя с ней. В гугле нашел советы персобирать ядро, пересобирать gcc… В общем мой уровень не позволяет такие сложности.

  Путь разума

  Первым делом решил проверить видит ли железку ядро. Вытаскиваю адаптер и втыкаю его в соседний разъем.

  . [ 1498.558445] usb 1-1.1: new high-speed USB device number 6 using ehci-pci [ 1498.667540] usb 1-1.1: New USB device found, idVendor=0bda, idProduct=a811 [ 1498.667544] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1498.667546] usb 1-1.1: Product: 802.11ac WLAN Adapter [ 1498.667548] usb 1-1.1: Manufacturer: Realtek [ 1498.667550] usb 1-1.1: SerialNumber: 00e04c000001 

  Ищу название драйвера на лазерном диске от производителя, вот оно: RTL8821AU_Linux_v5.2.6.3_25025_COEX20171103-6c6d.20171106.
  Подключаю смартфон в режиме модема и пробую в лоб:

  sk@ds:~$ sudo apt install realtek-88xxau-dkms [sudo] password fоr sk: Чтение списков пакетов… Готово Построение дерева зависимостей Чтение информации о состоянии… Готово E: Невозможно найти пакет realtek-88xxau-dkms

  Видимо репозиторий моего дистрибутива к такому не готов. Захожу на гитхаб и качаю исправленную версию драйвера.

  Распаковываю, нахожу dkms-install.sh, запускаю его. Драйвер установлен.
  Не будучи гуру linux не стал разбираться с остановкой и запуском адаптера, ввел:

  Источник

  Читайте также:  Linux права папок chmod