Changes for page Cellular network connection details and tips

Last modified by Kilight Cao on 2024/12/31 16:38

From version < 82.2 >

edited by Xiaoling
on 2023/03/23 17:38

To version < 84.1 >

edited by Edwin Chen
on 2023/05/05 08:21

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.Xiaoling
++XWiki.Edwin

Content

@@ -9,7 +9,7 @@
  = 1. Enable Cellular Connection =
--//If your device has a Cellular module, you can see the below screenshot. enable the cellular connection here.//
++If your device has a Cellular module, you can see the below screenshot. enable the cellular connection here.
  [[image:image-20220601110850-2.png]]
@@ -17,7 +17,7 @@
  (((
--//If your device doesn't have a cellular module, you will see a cellular module not detected.//
++If your device doesn't have a cellular module, you will see a cellular module not detected.
  )))
  [[image:image-20220527153544-2.png]]
@@ -26,13 +26,13 @@
  = 2. How to Debug if Cellular connection fails =
--//If there is a problem with the cellular connection. Please check the below points~://
++If there is a problem with the cellular connection. Please check the below points:
  == 2.1 Do you order the model with a cellular option ==
--//Make sure you order the model with the cellular option. Can check by command or via the Web UI.//
++Make sure you order the model with the cellular option. Can check by command or via the Web UI.
  (% class="box" %)
  (((
@@ -48,10 +48,10 @@
  == 2.2 Do you input the SIM card correctly ==
--**//Below command can check if you have a SIM card inserted, or via Web UI//**
++**Below command can check if you have a SIM card inserted, or via Web UI**
--* //Make sure to Power Off when you insert the SIM card and power on the device. The device doesn't support auto-detect SIM card on power on//
--* //Make sure you have the correct direction to insert the SIM card. Every device has an example photo in the manual for the direction.//
++* Make sure to Power Off when you insert the SIM card and power on the device. The device doesn't support auto-detect SIM card on power on
++* Make sure you have the correct direction to insert the SIM card. Every device has an example photo in the manual for the direction.
  (% class="box" %)
  (((
@@ -68,10 +68,10 @@
  (% class="wikigeneratedid" %)
--//**(% style="color:red" %)Note:(%%)**(% style="color:red" %) **If the icon is missing some information, like SIM, Network, or Signal, which may be due to the display bug.**//
++**(% style="color:red" %)Note:(%%)**(% style="color:red" %) **If the icon is missing some information, like SIM, Network, or Signal, which may be due to the display bug.**
  (% class="wikigeneratedid" %)
--//Please check the IP address is displayed and the Internet displays "OK", it works properly.//
++Please check the IP address is displayed and the Internet displays "OK", it works properly.
  (% class="wikigeneratedid" %)
  [[image:image-20220527153827-5.png]]
@@ -80,7 +80,7 @@
  == 2.3 Check dialing info ==
--//run "**logread -f**" in gateway CLI。//
++run "**logread -f**" in gateway CLI。
  (% class="box" %)
  (((
@@ -128,9 +128,9 @@
  === 2.4.1 The gateway can read the SIM card, But the Internet is displayed as Fail. ===
--//Users can check whether the APN matched by the SIM card is correct.//
++Users can check whether the APN matched by the SIM card is correct.
--//Regarding what APN your SIM card should use, Users can search for the APN corresponding to the SIM card by Google or ask the carrier.//
++Regarding what APN your SIM card should use, Users can search for the APN corresponding to the SIM card by Google or ask the carrier.
  [[image:image-20220718155937-1.png||height="562" width="497"]]
@@ -139,7 +139,7 @@
  === 2.4.2 The gateway can read the SIM card, But the Internet is displayed as Fail, and at the same time Network displays the carrier network. ===
--//It should be SIM card no flow, users can insert SIM cards into the mobile phone for testing.//
++It should be SIM card no flow, users can insert SIM cards into the mobile phone for testing.
  [[image:1658131428288-728.png||height="538" width="494"]]
@@ -148,7 +148,7 @@
  === 2.4.3 The gateway can't read the SIM card, and the Internet is displayed as Fail. ===
--//Users need to check whether the SIM card type is suitable for the EC25 module.//
++Users need to check whether the SIM card type is suitable for the EC25 module.
  [[image:1658131612484-845.png||height="549" width="499"]]
@@ -157,7 +157,7 @@
  === 2.4.4 SIM display：~*~**SIM ERROR~*~** Check SIM is inserted test SIM in a mobile phone？ ===
--//Users can insert SIM cards into the mobile phone for testing.//
++Users can insert SIM cards into the mobile phone for testing.
  [[image:image-20220718160804-3.png||height="602" width="500"]]
@@ -167,7 +167,7 @@
  (((
--//By default, the Cellular Network won't be shared with the WiFi or LAN clients. If users need to share with them, the user can modify the file.//
++By default, the Cellular Network won't be shared with the WiFi or LAN clients. If users need to share with them, the user can modify the file.
  )))
  (% class="box" %)
@@ -204,18 +204,17 @@
  )))
  (((
--//and run **/etc/init.d/firewall reload** or reboot the device.//
++and run **/etc/init.d/firewall reload** or **reboot the device**.
  = 4. Switching between Cellular and Ethernet and Wi-Fi networks =
--//By default, Cell is the backup WAN where the Ethernet or Wi-Fi network is used first if they are available.//
++By default, Cell is the backup WAN where the Ethernet or Wi-Fi network is used first if they are available.
--//Once the Ethernet of the Wi-Fi network is unavailable where the gateway network will switch to a Cell network from Ethernet or Wi-Fi.//
++Once the Ethernet of the Wi-Fi network is unavailable where the gateway network will switch to a Cell network from Ethernet or Wi-Fi.
--
  **Enable Cellular and connect Ethernet at the same time**
  ETH icon is displayed as  [[image:1658135519305-444.png||height="18" width="19"]] Indicates that Ethernet is the main working network.
@@ -226,12 +226,12 @@
  == 4.1 Switching between Cellular and Ethernet networks ==
--//When connecting to the AP WiFI of the gateway, users can access the Web UI of the gateway through the default address 10.130.1.1//
++When connecting to the AP WiFI of the gateway, users can access the Web UI of the gateway through the default address 10.130.1.1
  [[image:image-20220606140622-2.png||height="664" width="1106"]]
--//**Remove the network cable from the WAN port on the gateway, the gateway will switch to a Cellular network.**//
++**Remove the network cable from the WAN port on the gateway, the gateway will switch to a Cellular network.**
  [[image:image-20220606140859-4.png||height="687" width="1107"]]
@@ -241,17 +241,17 @@
  (% class="wikigeneratedid" %)
--//Enable **Cellular** and connect **WiFi** at the same time//
++Enable **Cellular** and connect **WiFi** at the same time
--//WiFi icon is displayed as //[[image:1658135519305-444.png||height="23" width="24"]]  Indicates that WiFi is the main working network.
++WiFi icon is displayed as [[image:1658135519305-444.png||height="23" width="24"]]  Indicates that WiFi is the main working network.
--//Cell icon is displayed as  //[[image:1658135500498-725.png||height="23" width="22"]]// Indicates that Cellular is the backup WAN.//
++Cell icon is displayed as  [[image:1658135500498-725.png||height="23" width="22"]] Indicates that Cellular is the backup WAN.
  [[image:image-20220606141113-7.png||height="678" width="1106"]]
--//**Close the WiFi WAN, the gateway will switch to a Cellular network.**//
++**Close the WiFi WAN, the gateway will switch to a Cellular network.**
  [[image:image-20220606140932-5.png||height="687" width="1107"]]
@@ -283,12 +283,12 @@
  == **How does the gateway access the Quetel module directly (to send AT commands)** ==
--//Users can access the gateway CLI and run the minicom command to get the configuration interface.//
++Users can access the gateway CLI and run the minicom command to get the configuration interface.
  (((
--**//Enter the minicom command, then select the option ''serial port setup".//**
++**Enter the minicom command, then select the option ''serial port setup".**
  )))
  (% class="box infomessage" %)
@@ -309,7 +309,7 @@
  )))
--(% style="color:red" %)//**Note: Enter the corresponding letter to change the configuration, like A,B,C**//
++(% style="color:red" %)**Note: Enter the corresponding letter to change the configuration, like A,B,C**
  [[image:image-20220527154154-7.png]]
@@ -318,11 +318,11 @@
  (((
--//Enter (% style="color:blue" %)**AT+GSN **(%%)in the interface to get the IMEI,//
++Enter (% style="color:blue" %)**AT+GSN **(%%)in the interface to get the IMEI,
  )))
  (((
--//**For example: (% style="color:#037691" %)860548042566627(%%)**//
++**For example: (% style="color:#037691" %)860548042566627(%%)**
  )))
  (% class="box infomessage" %)
@@ -339,11 +339,11 @@
  (((
--//Enter (% style="color:blue" %)**AT+QCCID **(%%)in the interface to get the ICCID,//
++Enter (% style="color:blue" %)**AT+QCCID **(%%)in the interface to get the ICCID,
  )))
  (((
--//**For example: (% style="color:#037691" %)89860118005400261748(%%)**//
++**For example: (% style="color:#037691" %)89860118005400261748(%%)**
  (% class="box infomessage" %)
  (((
@@ -359,22 +359,22 @@
  == 6.1 Introduction ==
--(% style="color:red" %)**//Prerequisite: Requires a USB 4G Dongle and a supported gateway firmware//**
++(% style="color:red" %)**Prerequisite: Requires a USB 4G Dongle and a supported gateway firmware**
  (((
--//This introduces a setup and configured gateway for using a USB 3g/UMTS-modem for WAN connection.//
++This introduces a setup and configured gateway for using a USB 3g/UMTS-modem for WAN connection.
  )))
  (((
--//Many modes (and most **LTE**) USB modems provide **qmi**, **mbim**, **ncm**, **rndis** protocol for connection instead of legacy **ppp** protocol, they are faster and better, overall recommended.//
++Many modes (and most **LTE**) USB modems provide **qmi**, **mbim**, **ncm**, **rndis** protocol for connection instead of legacy **ppp** protocol, they are faster and better, overall recommended.
  )))
  (((
--//This is not beginner-friendly due to too many protocols.//
++This is not beginner-friendly due to too many protocols.
--//For more information: [[https:~~/~~/openwrt.org/docs/guide-user/network/wan/wwan/3gdongle>>url:https://openwrt.org/docs/guide-user/network/wan/wwan/3gdongle]]//
++For more information: [[https:~~/~~/openwrt.org/docs/guide-user/network/wan/wwan/3gdongle>>url:https://openwrt.org/docs/guide-user/network/wan/wwan/3gdongle]]
  )))
@@ -382,10 +382,10 @@
  == 6.2 How to use the USB Dongle at the gateway ==
--//Most of the products can be used on the gateway, but because their protocols are different, they are not used in the same way.//
++Most of the products can be used on the gateway, but because their protocols are different, they are not used in the same way.
  (((
--//For example, the Huawei-E3372/E8372 is using **Hilink mode** or **NCM mode**.//
++For example, the Huawei-E3372/E8372 is using **Hilink mode** or **NCM mode**.
  )))
  (% class="box" %)
@@ -409,15 +409,15 @@
  (((
--//USB-Dongle plugs into the gateway USB port//
++USB-Dongle plugs into the gateway USB port
  )))
  (((
--//Check the USB module via command (% style="color:#037691" %)**lsusb**//
++Check the USB module via command (% style="color:#037691" %)**lsusb**
  )))
  (((
--(% style="color:red" %)//**Note: Users need to that connect to the gateway command line via ssh.**//
++(% style="color:red" %)**Note: Users need to that connect to the gateway command line via ssh.**
  )))
  [[image:image-20220527154739-9.png]]
@@ -426,7 +426,7 @@
  === 6.3.2 Detection of new network interfaces added ===
--//Check network configuration command line input: //
++Check network configuration command line input:
  (% class="box infomessage" %)
  (((
@@ -437,9 +437,9 @@
  [[image:image-20220527154822-10.png]]
--//In the command, the output user can see that the new interface added is (% style="color:#037691" %)**eth2**//
++In the command, the output user can see that the new interface added is (% style="color:#037691" %)**eth2**
--//Usually, the user can see that the new interface added is (% style="color:#037691" %)**eth2** (% style="color:black" %)or (% style="color:#037691" %)**wwan0**//
++Usually, the user can see that the new interface added is (% style="color:#037691" %)**eth2** (% style="color:black" %)or (% style="color:#037691" %)**wwan0**
  === 6.3.3 Add the new interface to the network configuration. ===
@@ -467,7 +467,7 @@
  [[image:image-20220527155013-12.png]]
--//Now, Gateway is configured to access the internet on the LTE network.//
++Now, Gateway is configured to access the internet on the LTE network.
  == 6.4 NCM mode ==
@@ -478,42 +478,49 @@
  === 6.5.1 The USB-Dongle interface cannot obtain the IP address. ===
--//Please try this USB dongle to access the internet on your PC, to make sure this USB dongle can normally access the internet.//
++Please try this USB dongle to access the internet on your PC, to make sure this USB dongle can normally access the internet.
  = 7. How to reduce data traffic =
--== 7.1 Reduce Status Uplink Interval ==
++== 7.1 How the gateway will consume data traffic ==
++Below list the place where the data traffic will use.
--**//The gateways will use the data traffic below two places.//**
++* Valid uplink data to LoRaWAN server or IoT server. ( We can't reduce this as they are the data we want)
++* Invalid uplink sensor data to LoRaWAN serevr. ( See Filter unwanted packets)
++* LoRaWAN Status push or polling data to LoRaWAN server . ( We can reduce this part , see below for discussion)
++* System Keep Alive data. ( To ensure the system is more robust, can be disabled)
++* Auto update ( Software auto update, can be disabled)
++=== 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server ===
--//1. There is the data traffic from LoRa package Forward which were the gateway status package and sensor end node uplink/downlink.//
++When gateway connect to LoRaWAN server via LoRaWAN protocol, besides the sensor data uplink/downlink. gateway will still need to:
--//For this case, by default, the gateway will uplink self-status to the LoRaWAN server per the 30s. the users can adjust the interval time.//
++* Uplink self-status to the LoRaWAN server every 30s. the users can adjust **Keep Alive Period** as below
++* Check LoRaWAN server status every 5 seconds to see if there is valid downlink command to sensors. We don't provide WEB UI option to modify this time, because the modify of this settings will lead to fail on OTAA Join and Downlink commands.
  [[image:image-20220527155108-13.png]]
++=== 7.1.2 System Keep Alive data ===
--//2. There is the data traffic from the gateway check self-network status. by default, the gateway will check the network per 15s.//
++System Keep Alive Data is used to check gateway-network status and fix possible issue. Gateway will check every 15 seconds and generate traffic.
--//For this case, We have monitored the loss of data traffic, which is the loss of 2M data traffic per day. the users can adjust the interval time following screenshots.//
++Base on 15 seconds per check, the data traffic is about 2M data traffic per day. Users can adjust **Keepalive Interval** as below.
--[[image:image-20220527155358-16.png]]
++[[image:image-20220527155229-15.png||height="511" width="986"]]
--//System General interface//
++=== 7.1.3 Auto update ===
--[[image:image-20220527155229-15.png]]
++Gateway will check for update every day for new configure or software. User can disable them by below method.
--//Keepalive script interval time settings//
++=== 7.1.4 Filter unwanted packets ===
--== 7.2 Filter unwanted packets ==
++When gateway connect to LoRaWAN server via LoRaWAN protocol , Gateway will by default get every possible LoRaWAN packets and forward to LoRaWAN server. If there are sensors from others in the same area, such sensor data will also be forward to LoRaWAN server ( they will be ignore by the server). This also consume data.
--
  See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]]
@@ -537,6 +537,7 @@
  [[image:image-20221124135102-2.png]]
++
 . View the graphs and statistics using by going to **Statistics > Graphs** **> Interfaces > 3g-cellullar**
  [[image:image-20221124134927-1.png]]

Changes for page Cellular network connection details and tips

Summary

Details

Applications

Navigation