Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
docs:guide-user:network:wan:wwan:ethernetoverusb_rndis [2023/12/21 19:49] – [Use RNDIS USB Dongle for WAN connection] andrewzdocs: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://en.wikipedia.org/wiki/RNDIS|RNDIS]] (Remote Network Driver Interface Specification) is [[https://en.wikipedia.org/wiki/Ethernet_over_USB|ethernet over USB]] protocol used by some fast speed USB modems/dongles.+[[https://en.wikipedia.org/wiki/RNDIS|RNDIS]] (Remote Network Driver Interface Specification) is [[https://en.wikipedia.org/wiki/Ethernet_over_USB|Ethernet over USB]] protocol used by some USB modems
 + 
 +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://github.com/torvalds/linux/blob/master/drivers/net/usb/rndis_host.c|rndis_host Linux driver source code]]: Note from [[https://github.com/torvalds/linux/blob/master/drivers/net/usb/rndis_host.c|rndis_host Linux driver source code]]:
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) "Ethernet Emulation Model" (EEM). > USE OF RNDIS IS STRONGLY DISCOURAGED in favor of such non-proprietary alternatives as CDC Ethernet or the newer (and currently rare) "Ethernet Emulation Model" (EEM).
  
-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 "driverless", by conforming to RNDIS standard so they don't need a special driver just for themselves. These dongles lack any kind of interface or settings, they are just usb-to-ethernet adapters, nothing more.+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 dongles use to be "plug and play" or "driverless", by conforming to RNDIS standard so they don't need a special driver just for themselves. These dongles lack any kind of web interface or settings, they are just usb-to-ethernet adapters, nothing more.
  
 +Worth to add, the same protocol is widely used for [[docs:guide-user:network:wan:smartphone.usb.tethering|smartphone tethering]], so the same instructions are usually applicable for that use case as well.
  
-For more more information about different protocols used: + 
-  * **PPP**, see [[docs:guide-user:network:wan:wwan:3gdongle|How to use 3g/UMTS USB Dongle for WAN connection]]+For more information about other protocols commonly used:
   * **QMI** and **MBIM**, see [[docs:guide-user:network:wan:wwan:ltedongle|How to use LTE modem in QMI mode for WAN connection]]   * **QMI** and **MBIM**, see [[docs:guide-user:network:wan:wwan:ltedongle|How to use LTE modem in QMI mode for WAN connection]]
   * **NCM**, see [[docs:guide-user:network:wan:wwan:ethernetoverusb_ncm|How to use LTE modem in NCM mode for WAN connection]]   * **NCM**, see [[docs:guide-user:network:wan:wwan:ethernetoverusb_ncm|How to use LTE modem in NCM mode for WAN connection]]
 +  * **ECM**, see [[docs:guide-user:network:wan:wwan:ethernetoverusb_cdc|Use cdc_ether driver based dongles for WAN connection]]
 +  * **PPP**, see [[docs:guide-user:network:wan:wwan:3gdongle|How to use 3g/UMTS USB Dongle for WAN connection]]
  
 ===== 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 to an Alcatel Onetouch L850.).+For RNDIS device to work ''kmod-usb-net-rndis'' package needs to be installedInstall it either in Luci → System → Software or via command line: 
 +<code> 
 +root@OpenWrt:~# opkg update 
 +root@OpenWrt:~# opkg install kmod-usb-net-rndis 
 +</code>
  
-For RNDIS device to work ''kmod-usb-net-rndis'' package needs to be installed.+Additional modules will be automatically installed as //dependencies//.
  
-Install ''usb-modeswitch'' __if__ that is needed for switching the modem into a "working" state. More about: [[docs:guide-user:network:wan:wwan:usb-modeswitching|USB mode switch]]+You can also add the necessary packages when building a new image with [[https://firmware-selector.openwrt.org/|Firmware Selector]]. 
 + 
 +Install ''usb-modeswitch'' __only if__ that is needed for switching the modem into a "working" state. More about: [[docs:guide-user:network:wan:wwan:usb-modeswitching|USB mode switch]]
  
  
Line 33: Line 44:
 </code> </code>
  
-You can verify the interface details on the new ''usb0'' network interface by running ''ifconfig usb0''.+Note the interface name (''usb0'') mentioned on the last line, it will be used later. For another modem the name could be ''eth3'' or something like that.
  
 If the USB stick will be your only WAN connection, then the easiest way to set up the automatic connection is to change ''/etc/config/network'' to be something like:  If the USB stick will be your only WAN connection, then the easiest way to set up the automatic connection is to change ''/etc/config/network'' to be something like: 
Line 45: Line 56:
 (you need to reboot or restart the network subsystem with ''/etc/init.d/network restart'' afterwards) (you need to reboot or restart the network subsystem with ''/etc/init.d/network restart'' afterwards)
  
-Since RNDIS-based sticks create their own NAT'ed IP subnet, it is important that OpenWrt's LAN IP range is different from the modem'IP rangeIn the case of the Alcatel L850, the default range is 192.168.1.1, which clashes with OpenWrt's default. Therefore OpenWrt's LAN IP should be changed to something else, such as:+:!: Since RNDIS-based sticks create their own NAT'ed IP subnet, it is important that OpenWrt's LAN IP subnet is different from the modem'subnetFor some modems the default IP address is ''192.168.1.1'', which clashes with OpenWrt's default. Therefore if that address conflict cannot be resolved on the modem side, then OpenWrt's LAN IP subnet should be changed to something else, such as:
  
 <code> <code>
Line 52: Line 63:
 </code> </code>
  
-If auto-connect is disabled, or PIN-request is enabled on the 4G stick, you may have to visit the dongle's admin web interface (typically 192.168.1.1) to enter the PIN or initiate the 4G connection. You can do this from your PC connected to the OpenWrt WiFi.+==== 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 "dial" command to the AT command port, consult AT Commands Guide for the given modem for details. If this is the case it is worth trying to configure the [[docs:guide-user:network:wan:wwan:ethernetoverusb_ncm|NCM]] interface instead. 
 + 
 +If the modem exposes //serial// interfaces then the appropriate driver needs to be installed (''kmod-usb-serial'' or ''kmod-usb-serial-option'' or ''kmod-usb-serial-qualcomm'' or ''kmod-usb-acm'') as well as a simple //terminal// app like ''picocom''. More about: sending [[docs:guide-user:network:wan:wwan:at_commands|AT commands]] from the router. 
 + 
 +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 ''http://192.168.1.1'') to enter the PIN and/or initiate the connection. Modem's own IP address can be seen in the System Log: 
 +<code> 
 +daemon.notice netifd: wwan (20573): udhcpc: broadcasting discover 
 +daemon.notice netifd: wwan (20573): udhcpc: broadcasting select for 192.168.1.101, server 192.168.1.1 
 +daemon.notice netifd: wwan (20573): udhcpc: lease of 192.168.1.101 obtained from 192.168.1.1, lease time 43200 
 +daemon.notice netifd: Interface 'wwan' is now up 
 +</code> 
 + 
 +==== RNDIS Troubleshooting ====
  
 If you only see the USB messages, but not the rndis_host messages, then //modeswitching// may be at fault. If you only see the USB messages, but not the rndis_host messages, then //modeswitching// may be at fault.
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->Firewall->Custom Rules:+To protect it, you can add the following rule to Network->Firewall->Custom Rules (obsolete, needs to be converted to ''nftables'' rules):
  
 <code> <code>
Line 114: Line 137:
  
 and point your browser to http://localhost:8080. and point your browser to http://localhost:8080.
 +
  • Last modified: 2024/12/14 23:42
  • by andrewz