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 [2024/02/19 17:35] – [Use RNDIS USB Dongle for WAN connection] andrewz | 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:// |
| + | |||
| + | The same applies to external modems connected to USB ports ("dongles") and internal models installed into M.2(NGFF) or mPCIe slots. | ||
| Note from [[https:// | Note from [[https:// | ||
| Line 7: | Line 9: | ||
| > USE OF RNDIS IS STRONGLY DISCOURAGED in favor of such non-proprietary alternatives as CDC Ethernet or the newer (and currently rare) " | > USE OF RNDIS IS STRONGLY DISCOURAGED in favor of such non-proprietary alternatives as CDC Ethernet or the newer (and currently rare) " | ||
| - | It is also used by many USB3.0-GigabitEthernet-Adapter | + | It is also used by many USB3.0-GigabitEthernet-Adapters |
| + | |||
| + | Worth to add, the same protocol is widely used for [[docs: | ||
| Line 18: | Line 22: | ||
| ===== Setting up RNDIS-based dongles ===== | ===== Setting up RNDIS-based dongles ===== | ||
| - | (This section is based on experience with Bleeding Edge r47548 from December of 2015 on a wt3020 and connecting | + | For RNDIS device |
| + | < | ||
| + | root@OpenWrt: | ||
| + | root@OpenWrt: | ||
| + | </ | ||
| + | |||
| + | Additional modules will be automatically installed as // | ||
| - | For RNDIS device to work '' | + | You can also add the necessary packages when building a new image with [[https:// |
| - | Install '' | + | Install '' |
| Line 34: | 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 46: | 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 NAT'ed IP subnet, it is important that OpenWrt' | + | :!: Since RNDIS-based sticks create their own NAT'ed IP subnet, it is important that OpenWrt' |
| < | < | ||
| Line 53: | Line 63: | ||
| </ | </ | ||
| - | 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 the modem exposes //serial// interfaces then the appropriate driver needs to be installed ('' | ||
| + | |||
| + | 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 // | If you only see the USB messages, but not the rndis_host messages, then // | ||
| Line 99: | 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 115: | Line 137: | ||
| and point your browser to http:// | and point your browser to http:// | ||
| + | |||