Changes for page Cellular network connection details and tips

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

From version < 94.1 >

edited by Kilight Cao
on 2023/12/18 09:55

To version < 80.1 >

edited by Kilight Cao
on 2023/03/13 10:51

Change comment: Uploaded new attachment "1678675878256-777.png", version {1}

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 6 removed)

Details

Page properties

Content

@@ -6,10 +6,10 @@
--= 1. Enable Cellular Connection =
++= **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,23 +17,25 @@
  (((
--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]]
--= 2. How to Debug if Cellular connection fails =
++= **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.
++== **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.//
++
  (% class="box" %)
  (((
  //root@dragino-1bbd90:~~# lsusb
@@ -45,14 +45,15 @@
  [[image:image-20220601110748-1.png]]
--== 2.2 Do you input the SIM card correctly ==
++== **2.2 Do you input the SIM card correctly** ==
--**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.
++**//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.//
++
  (% class="box" %)
  (((
  //root@dragino-1dadd8:~~# **comgt -d /dev/ttyUSB3**
@@ -68,20 +68,21 @@
  (% 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]]
--== 2.3 Check dialing info ==
++== **2.3 Check dialing info** ==
--run "**logread -f**" in gateway CLI。
++//run "**logread -f**" in gateway CLI。//
++
  (% class="box" %)
  (((
  Fri Feb  7 01:20:28 2020 daemon.notice pppd[29452]: pppd 2.4.7 started by root, uid 0
@@ -123,51 +123,57 @@
  )))
--== 2.4 If the following situation occurs, how can users solve this problem? ==
--=== 2.4.1 The gateway can read the SIM card, But the Internet is displayed as Fail. ===
++== **2.4 If the following situation occurs, how can users solve this problem?** ==
--Users can check whether the APN matched by the SIM card is correct.
++=== **2.4.1 The gateway can read the SIM card, But the Internet is displayed as Fail.** ===
--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.
++//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.//
++
++
  [[image:image-20220718155937-1.png||height="562" width="497"]]
--=== 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. ===
++=== **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"]]
--=== 2.4.3 The gateway can't read the SIM card, and the Internet is displayed as Fail. ===
++=== **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"]]
--=== 2.4.4 SIM display：~*~**SIM ERROR~*~** Check SIM is inserted test SIM in a mobile phone？ ===
++=== **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"]]
--= 3. Share Cellular Network for WiFi & LAN clients =
++= **3. Share Cellular Network for WiFi & LAN clients** =
++
  (((
--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,17 +204,19 @@
  )))
  (((
--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 =
++= **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.
--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.
++//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.//
++
++
  **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.
@@ -222,87 +222,77 @@
  Cell icon is displayed as   [[image:1658135500498-725.png||height="17" width="17"]]  Indicates that Cellular is the backup WAN.
--== 4.1 Switching between Cellular and Ethernet networks ==
++(% style="display:none" %)  (%%)
++== **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"]]
  (% style="display:none" %) (%%)
--== 4.2 Switching between Cellular and WiFi networks ==
++== **4.2 Switching between Cellular and WiFi networks** ==
++
  (% 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"]]
--== 4.3 At the same time start Cellular and Ethernet and Wi-Fi networks ==
++== **4.3 At the same time start Cellular and Ethernet and Wi-Fi networks** ==
++
  [[image:image-20220606140328-1.png||height="682" width="1108"]]
++
  )))
--= 5. How does the gateway view the International Mobile Equipment Identity (IMEI) =
++= **5. How does the gateway view the International Mobile Equipment Identity (IMEI)** =
--=== For LIG16,LPS8, LPS8N, LG308, LG308N, DLOS8, DLOS8N view the International Mobile Equipment Identity (IMEI) ===
--
  Users can get the IMEI via Linux command, but you have to access the gateway CLI.
  (% class="box infomessage" %)
  (((
--**root@dragino-24b3c8:~~# comgt -d /dev/ttyModemAT -s /etc/gcom/getimei.gcom **
++**root@dragino-1b7c4c:~~# comgt -d /dev/ttyModemAT -s /etc/gcom/getimsi.gcom **
  )))
--[[image:image-20231218095203-4.png]]
++[[image:image-20221027140604-1.png||height="330" width="707"]]
--[[image:image-20231218095426-6.jpeg||height="466" width="990"]]
++[[image:image-20221027151146-2.png||height="554" width="1000"]]
--=== For LPS8v2 view the International Mobile Equipment Identity (IMEI) ===
--
--(% class="box infomessage" %)
--(((
--**root@dragino-e4e891:~~# /usr/local/dragino/cell/getinfo.sh**
--)))
--
--[[image:image-20231218094526-1.png]]
--
--
--[[image:image-20231218094741-3.png]]
--
--
  == **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" %)
@@ -323,20 +323,17 @@
  )))
--(% 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]]
--=== **International Mobile Equipment Identity (IMEI)** ===
--
--
  (((
--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" %)
@@ -349,57 +349,41 @@
  [[image:image-20220527154231-8.png]]
--=== **Integrated Circuit Card Identifier (ICCID)** ===
++= **6. How does the gateway connect to the network via a USB 4G Dongle** =
--(((
--Enter (% style="color:blue" %)**AT+QCCID **(%%)in the interface to get the ICCID,
--)))
--(((
--**For example: (% style="color:#037691" %)89860118005400261748(%%)**
++== **6.1 Introduction** ==
--(% class="box infomessage" %)
--(((
-- **AT+QCCID**
--)))
--)))
--[[image:1678675878256-777.png]]
++(% style="color:red" %)**//Prerequisite: Requires a USB 4G Dongle and a supported gateway firmware//**
--
--= 6. How does the gateway connect to the network via a USB 4G Dongle =
--
--== 6.1 Introduction ==
--
--
--(% 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]]//
++
  )))
--== 6.2 How to use the USB Dongle at the gateway ==
++== **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" %)
@@ -413,35 +413,38 @@
  )))
--== 6.3 Hilink mode ==
++== **6.3 Hilink mode** ==
++
  //Gateway upgrade to the specified firmware:[[Hilink.mode~~-~~-build-v5.4.1625627505>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LG308-LG301/Firmware/USB-Dongle_firmware/Hilink.mode--build-v5.4.1625627505-20210707-1113/]]//
--=== 6.3.1 Plugs into the device ===
++=== **6.3.1 Plugs into the device** ===
++
  (((
--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]]
--=== 6.3.2 Detection of new network interfaces added ===
++=== **6.3.2 Detection of new network interfaces added** ===
--Check network configuration command line input:
++//Check network configuration command line input: //
++
  (% class="box infomessage" %)
  (((
  (((
@@ -451,14 +451,15 @@
  [[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. ===
++=== **6.3.3 Add the new interface to the network configuration.** ===
++
  //Enter the configuration from the command line~://
  (% class="box" %)
@@ -481,76 +481,64 @@
  [[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 ==
++== **6.4 NCM mode** ==
--== 6.5 Troubleshooting ==
--=== 6.5.1 The USB-Dongle interface cannot obtain the IP address. ===
++== **6.5 Troubleshooting** ==
--Please try this USB dongle to access the internet on your PC, to make sure this USB dongle can normally access the internet.
++=== **6.5.1 The USB-Dongle interface cannot obtain the IP address.** ===
--= 7. How to reduce data traffic =
++//Please try this USB dongle to access the internet on your PC, to make sure this USB dongle can normally access the internet.//
--== 7.1 How the gateway will consume data traffic ==
--Below list the place where the data traffic will use.
--* 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)
--* system Time synchronization Checking
--* Auto update ( Software auto update, can be disabled)
++= **7. How to reduce data traffic** =
--=== 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server ===
--When gateway connect to LoRaWAN server via LoRaWAN protocol, besides the sensor data uplink/downlink. gateway will still need to:
++== **7.1 Reduce Status Uplink Interval** ==
--* 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]]
++**//The gateways will use the data traffic below two places.//**
--=== 7.1.2 System Keep Alive data ===
++//1. There is the data traffic from LoRa package Forward which were the gateway status package and sensor end node uplink/downlink.//
--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, by default, the gateway will uplink self-status to the LoRaWAN server per the 30s. the users can adjust the interval time.//
--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-20220527155108-13.png]]
--[[image:image-20220527155229-15.png||height="511" width="986"]]
--=== 7.1.3 Auto update ===
++//2. There is the data traffic from the gateway check self-network status. by default, the gateway will check the network per 15s.//
--Gateway will check for update every day for new configure or software. User can disable them by below method.
++//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.//
++[[image:image-20220527155358-16.png]]
--=== 7.1.4 Filter unwanted packets ===
++//System General interface//
--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]]
++[[image:image-20220527155229-15.png]]
++//Keepalive script interval time settings//
--== 7.2 Usage statistics ==
--=== 7.2.1 How does Openwrt usage statistics ===
++== **7.2 Filter unwanted packets** ==
--This is a general instruction for the use of Openwrt of Dragino devices. Current models include:
--* LPS8,LPS8N
--* LG308,LG308N
--* DLOS8,DLOS8N
--* LIG16
++See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]]
++
++== **7.3 Usage statistics** ==
++
++
  ~1. Activate LuCI and connect to SSH following [[these instructions>>doc:Main.Install Luci in the new UI firmware.WebHome]]
 . Install luci-app-statistics using the following terminal commands:
@@ -568,7 +568,6 @@
  [[image:image-20221124135102-2.png]]
--
 . View the graphs and statistics using by going to **Statistics > Graphs** **> Interfaces > 3g-cellullar**
  [[image:image-20221124134927-1.png]]

image-20231218094526-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-23.3 KB

Content

image-20231218094728-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-38.2 KB

Content

image-20231218094741-3.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-47.5 KB

Content

image-20231218095203-4.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-18.5 KB

Content

image-20231218095257-5.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-73.0 KB

Content

image-20231218095426-6.jpeg

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-53.7 KB

Content

Changes for page Cellular network connection details and tips

Summary

Details

Applications

Navigation