Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| docs:guide-user:network:wan:wwan:ethernetoverusb_rndis [2018/04/25 13:45] – added line about this protocol being used by gigabit ethernet dongles bobafetthotmail | docs:guide-user:network:wan:wwan:ethernetoverusb_rndis [2024/12/14 23:42] (current) – [Additional steps] andrewz | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Use RNDIS USB Dongle for WAN connection ====== | ====== Use RNDIS USB Dongle for WAN connection ====== | ||
| - | [[https:// | + | [[https:// |
| - | It is also used by many USB3.0-GigabitEthernet-Adapter like the TP-Link UE300 and all chinese low-cost ones I bought on ebay. It is one of the ways these gigabit ethernet dongles use to be "plug and play" or " | + | The same applies |
| + | Note from [[https:// | ||
| - | For more more information about different protocols used: | + | > USE OF RNDIS IS STRONGLY DISCOURAGED in favor of such non-proprietary alternatives as CDC Ethernet or the newer (and currently rare) " |
| - | * **ppp**, see [[docs: | + | |
| - | * **qmi** | + | |
| - | * **ncm**, see [[docs: | + | |
| - | ===== Setting up RNDIS-based dongles | + | It is also used by many USB3.0-GigabitEthernet-Adapters like the TP-Link UE300 and all Chinese low-cost ones you can buy on ebay, etc. It is one of the ways these gigabit ethernet |
| - | (This section is based on experience with Bleeding Edge r47548 from December of 2015 on a wt3020 and connecting | + | Worth to add, the same protocol is widely used for [[docs: |
| - | For rndis devices, only a limited subset of packages are necessary (besides the base USB packages, that are most likely already contained in the base image): | ||
| + | For more information about other protocols commonly used: | ||
| + | * **QMI** and **MBIM**, see [[docs: | ||
| + | * **NCM**, see [[docs: | ||
| + | * **ECM**, see [[docs: | ||
| + | * **PPP**, see [[docs: | ||
| + | |||
| + | ===== Setting up RNDIS-based dongles ===== | ||
| + | |||
| + | For RNDIS device to work '' | ||
| < | < | ||
| - | opkg update | + | root@OpenWrt: |
| - | opkg install kmod-usb-net-rndis | + | root@OpenWrt: |
| </ | </ | ||
| - | kmod-usb-net-rndis | + | Additional modules |
| + | |||
| + | You can also add the necessary packages when building a new image with [[https:// | ||
| + | |||
| + | Install '' | ||
| - | After installing the packages and connecting the USB stick, the following should appear in dmesg: | + | After installing the packages and connecting the USB stick, the following should appear in '' |
| < | < | ||
| Line 33: | Line 44: | ||
| </ | </ | ||
| - | You can verify | + | Note the interface |
| - | If the USB stick will be your only WAN connection, then the easiest way to set up the automatic connection is to change / | + | If the USB stick will be your only WAN connection, then the easiest way to set up the automatic connection is to change |
| < | < | ||
| Line 45: | Line 56: | ||
| (you need to reboot or restart the network subsystem with ''/ | (you need to reboot or restart the network subsystem with ''/ | ||
| - | Since RNDIS-based sticks create their own NATted | + | :!: Since RNDIS-based sticks create their own NAT' |
| < | < | ||
| config interface ' | config interface ' | ||
| - | option ipaddr '10.10.10.1' | + | option ipaddr '192.168.10.1' |
| </ | </ | ||
| - | If auto-connect is disabled, or PIN-request is enabled on the 4G stick, you may have to visit the dongle' | + | ==== Additional steps ==== |
| - | === RNDIS Troubleshooting === | + | For some modems adding the network interface will be sufficient, but others may need an APN provisioned. It is also sometimes necessary to send a special " |
| - | If you only see the usb messages, but not the rndis_host messages, | + | If the modem exposes //serial// interfaces |
| - | Checking / | + | If auto-connect is disabled or PIN-request is enabled on the modem or correct APN needs to be set, you may need to visit its admin web interface (typically at '' |
| + | < | ||
| + | daemon.notice netifd: wwan (20573): udhcpc: broadcasting discover | ||
| + | daemon.notice netifd: wwan (20573): udhcpc: broadcasting select for 192.168.1.101, | ||
| + | daemon.notice netifd: wwan (20573): udhcpc: lease of 192.168.1.101 obtained from 192.168.1.1, | ||
| + | daemon.notice netifd: Interface ' | ||
| + | </ | ||
| + | |||
| + | ==== RNDIS Troubleshooting ==== | ||
| + | |||
| + | If you only see the USB messages, but not the rndis_host messages, then // | ||
| + | |||
| + | Checking | ||
| < | < | ||
| Line 98: | Line 121: | ||
| - | === RNDIS Security Note === | + | ==== RNDIS Security Note ==== |
| :!: Leaving your RNDIS-based dongle admin web interface available to LAN users might not be something you would like to do, as there is usually no authentication mechanism there. | :!: Leaving your RNDIS-based dongle admin web interface available to LAN users might not be something you would like to do, as there is usually no authentication mechanism there. | ||
| - | To protect it, you can add the following rule to Network-> | + | To protect it, you can add the following rule to Network-> |
| < | < | ||
| Line 107: | Line 130: | ||
| </ | </ | ||
| - | Now, if you need to access your dongle web interface, log in to your OpenWRT | + | Now, if you need to access your dongle web interface, log in to your OpenWrt |
| < | < | ||
| Line 114: | Line 137: | ||
| and point your browser to http:// | and point your browser to http:// | ||
| + | |||