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 [2024/12/04 10:20] – [Setting up RNDIS-based dongles] andrewzdocs:guide-user:network:wan:wwan:ethernetoverusb_rndis [2024/12/14 23:42] (current) – [Additional steps] andrewz
Line 56: 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 subnet is different from the modem's subnet. For some modems the default IP address is ''192.168.1.1'', which clashes with OpenWrt's default. Therefore if that cannot be resolved on the modem side, then OpenWrt's LAN IP subnet 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's subnet. For 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 65: Line 65:
 ==== Additional steps ==== ==== Additional steps ====
  
-For some modems adding an 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.+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 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 disabledor PIN-request is enabled on the modem, 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.+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 ==== ==== RNDIS Troubleshooting ====
  • Last modified: 2024/12/14 23:42
  • by andrewz