Wiki source code of Cellular network connection details and tips
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | |||
2 | |||
3 | **Table of Contents:** | ||
4 | |||
5 | {{toc/}} | ||
6 | |||
7 | |||
8 | |||
9 | = 1. Enable Cellular Connection = | ||
10 | |||
11 | |||
12 | //If your device has a Cellular module, you can see the below screenshot. enable the cellular connection here.// | ||
13 | |||
14 | [[image:image-20220601110850-2.png]] | ||
15 | |||
16 | **//Enable Cellular Connection//** | ||
17 | |||
18 | |||
19 | ((( | ||
20 | //If your device doesn't have a cellular module, you will see a cellular module not detected.// | ||
21 | ))) | ||
22 | |||
23 | [[image:image-20220527153544-2.png]] | ||
24 | |||
25 | |||
26 | = 2. How to Debug if Cellular connection fails = | ||
27 | |||
28 | |||
29 | //If there is a problem with the cellular connection. Please check the below points~:// | ||
30 | |||
31 | |||
32 | == 2.1 Do you order the model with a cellular option == | ||
33 | |||
34 | |||
35 | //Make sure you order the model with the cellular option. Can check by command or via the Web UI.// | ||
36 | |||
37 | (% class="box" %) | ||
38 | ((( | ||
39 | //root@dragino-1bbd90:~~# lsusb | ||
40 | Bus 001 Device 004: ID 2c7c:0125 ~-~-> This is the Cellular module | ||
41 | Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub | ||
42 | Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub// | ||
43 | ))) | ||
44 | |||
45 | [[image:image-20220601110748-1.png]] | ||
46 | |||
47 | |||
48 | == 2.2 Do you input the SIM card correctly == | ||
49 | |||
50 | |||
51 | **//Below command can check if you have a SIM card inserted, or via Web UI//** | ||
52 | |||
53 | * //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// | ||
54 | * //Make sure you have the correct direction to insert the SIM card. Every device has an example photo in the manual for the direction.// | ||
55 | |||
56 | (% class="box" %) | ||
57 | ((( | ||
58 | //root@dragino-1dadd8:~~# **comgt -d /dev/ttyUSB3** | ||
59 | SIM ready | ||
60 | Waiting for Registration..(120 sec max) | ||
61 | Registered on Home network: "CHN-UNICOM",7 | ||
62 | Signal Quality: 10,99// | ||
63 | ))) | ||
64 | |||
65 | |||
66 | (% class="wikigeneratedid" %) | ||
67 | [[image:image-20220527153804-4.png]] | ||
68 | |||
69 | |||
70 | (% class="wikigeneratedid" %) | ||
71 | //**(% 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.**// | ||
72 | |||
73 | (% class="wikigeneratedid" %) | ||
74 | //Please check the IP address is displayed and the Internet displays "OK", it works properly.// | ||
75 | |||
76 | (% class="wikigeneratedid" %) | ||
77 | [[image:image-20220527153827-5.png]] | ||
78 | |||
79 | |||
80 | == 2.3 Check dialing info == | ||
81 | |||
82 | |||
83 | //run "**logread -f**" in gateway CLI。// | ||
84 | |||
85 | (% class="box" %) | ||
86 | ((( | ||
87 | Fri Feb 7 01:20:28 2020 daemon.notice pppd[29452]: pppd 2.4.7 started by root, uid 0 | ||
88 | Fri Feb 7 01:20:29 2020 user.notice iot_keep_alive: Ping WAN | ||
89 | Fri Feb 7 01:20:29 2020 user.notice iot_keep_alive: Default interface is | ||
90 | Fri Feb 7 01:20:29 2020 user.notice iot_keep_alive: No internet at any interface | ||
91 | Fri Feb 7 01:20:29 2020 local2.info chat[29485]: abort on (BUSY) | ||
92 | Fri Feb 7 01:20:29 2020 local2.info chat[29485]: abort on (NO CARRIER) | ||
93 | Fri Feb 7 01:20:29 2020 local2.info chat[29485]: abort on (ERROR) | ||
94 | Fri Feb 7 01:20:29 2020 local2.info chat[29485]: report (CONNECT) | ||
95 | Fri Feb 7 01:20:29 2020 local2.info chat[29485]: timeout set to 10 seconds | ||
96 | Fri Feb 7 01:20:29 2020 local2.info chat[29485]: send (AT&F^M) | ||
97 | Fri Feb 7 01:20:29 2020 local2.info chat[29485]: expect (OK) | ||
98 | Fri Feb 7 01:20:29 2020 local2.info chat[29485]: AT&F^M^M | ||
99 | Fri Feb 7 01:20:29 2020 local2.info chat[29485]: OK | ||
100 | Fri Feb 7 01:20:29 2020 local2.info chat[29485]: ~-~- got it | ||
101 | Fri Feb 7 01:20:29 2020 local2.info chat[29485]: send (ATE1^M) | ||
102 | Fri Feb 7 01:20:29 2020 local2.info chat[29485]: expect (OK) | ||
103 | Fri Feb 7 01:20:29 2020 local2.info chat[29485]: ^M | ||
104 | Fri Feb 7 01:20:29 2020 local2.info chat[29485]: ATE1^M^M | ||
105 | Fri Feb 7 01:20:29 2020 local2.info chat[29485]: OK | ||
106 | Fri Feb 7 01:20:29 2020 local2.info chat[29485]: ~-~- got it | ||
107 | Fri Feb 7 01:20:29 2020 local2.info chat[29485]: send (AT+CGDCONT=1,"IP",""^M) | ||
108 | Fri Feb 7 01:20:30 2020 local2.info chat[29485]: timeout set to 30 seconds | ||
109 | Fri Feb 7 01:20:30 2020 local2.info chat[29485]: expect (OK) | ||
110 | Fri Feb 7 01:20:30 2020 local2.info chat[29485]: ^M | ||
111 | Fri Feb 7 01:20:30 2020 local2.info chat[29485]: AT+CGDCONT=1,"IP",""^M^M | ||
112 | Fri Feb 7 01:20:30 2020 local2.info chat[29485]: OK | ||
113 | Fri Feb 7 01:20:30 2020 local2.info chat[29485]: ~-~- got it | ||
114 | (% style="color:#037691" %)**Fri Feb 7 01:20:30 2020 local2.info chat[29485]: send (ATD*99#^M) ~-~-~-~--> In case the dialling process already reach here. | ||
115 | Normally the problem is with a provider, need to check if the SIM card has balance or other requirement from the cellular operator**(%%) | ||
116 | (% style="color:black" %)Fri Feb 7 01:20:30 2020 local2.info chat[29485]: expect (CONNECT) | ||
117 | Fri Feb 7 01:20:30 2020 local2.info chat[29485]: ^M | ||
118 | Fri Feb 7 01:20:30 2020 local2.info chat[29485]: ATD*99#^M^M | ||
119 | Fri Feb 7 01:20:30 2020 local2.info chat[29485]: CONNECT | ||
120 | Fri Feb 7 01:20:30 2020 local2.info chat[29485]: ~-~- got it | ||
121 | Fri Feb 7 01:20:30 2020 local2.info chat[29485]: send ( ^M) | ||
122 | Fri Feb 7 01:20:30 2020 daemon.info pppd[29452]: Serial connection established. | ||
123 | ))) | ||
124 | |||
125 | |||
126 | == 2.4 If the following situation occurs, how can users solve this problem? == | ||
127 | |||
128 | === 2.4.1 The gateway can read the SIM card, But the Internet is displayed as Fail. === | ||
129 | |||
130 | |||
131 | //Users can check whether the APN matched by the SIM card is correct.// | ||
132 | |||
133 | //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.// | ||
134 | |||
135 | |||
136 | [[image:image-20220718155937-1.png||height="562" width="497"]] | ||
137 | |||
138 | |||
139 | === 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. === | ||
140 | |||
141 | |||
142 | //It should be SIM card no flow, users can insert SIM cards into the mobile phone for testing.// | ||
143 | |||
144 | |||
145 | [[image:1658131428288-728.png||height="538" width="494"]] | ||
146 | |||
147 | |||
148 | === 2.4.3 The gateway can't read the SIM card, and the Internet is displayed as Fail. === | ||
149 | |||
150 | |||
151 | //Users need to check whether the SIM card type is suitable for the EC25 module.// | ||
152 | |||
153 | |||
154 | [[image:1658131612484-845.png||height="549" width="499"]] | ||
155 | |||
156 | |||
157 | === 2.4.4 SIM display:~*~**SIM ERROR~*~** Check SIM is inserted test SIM in a mobile phone? === | ||
158 | |||
159 | |||
160 | //Users can insert SIM cards into the mobile phone for testing.// | ||
161 | |||
162 | |||
163 | [[image:image-20220718160804-3.png||height="602" width="500"]] | ||
164 | |||
165 | |||
166 | = 3. Share Cellular Network for WiFi & LAN clients = | ||
167 | |||
168 | |||
169 | ((( | ||
170 | //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.// | ||
171 | ))) | ||
172 | |||
173 | (% class="box" %) | ||
174 | ((( | ||
175 | ((( | ||
176 | root@dragino-1d25dc:~~# cat /etc/config/firewall | ||
177 | |||
178 | config defaults | ||
179 | option syn_flood '1' | ||
180 | option input 'ACCEPT' | ||
181 | option output 'ACCEPT' | ||
182 | option forward 'REJECT' | ||
183 | config zone | ||
184 | option name 'lan' | ||
185 | list network 'lan' | ||
186 | option input 'ACCEPT' | ||
187 | option output 'ACCEPT' | ||
188 | option forward 'REJECT' | ||
189 | config zone | ||
190 | option name 'wan' | ||
191 | list network 'wan' | ||
192 | list network 'wwan' | ||
193 | list network 'wan6' | ||
194 | list network 'cellular' ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--> Add this line and reboot | ||
195 | option input 'REJECT' | ||
196 | option output 'ACCEPT' | ||
197 | option forward 'ACCEPT' | ||
198 | option masq '1' | ||
199 | option mtu_fix '1' | ||
200 | config forwarding | ||
201 | option src 'lan' | ||
202 | option dest 'wan' | ||
203 | ))) | ||
204 | ))) | ||
205 | |||
206 | ((( | ||
207 | //and run **/etc/init.d/firewall reload** or reboot the device.// | ||
208 | |||
209 | |||
210 | = 4. Switching between Cellular and Ethernet and Wi-Fi networks = | ||
211 | |||
212 | |||
213 | //By default, Cell is the backup WAN where the Ethernet or Wi-Fi network is used first if they are available.// | ||
214 | |||
215 | //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.// | ||
216 | |||
217 | |||
218 | |||
219 | **Enable Cellular and connect Ethernet at the same time** | ||
220 | |||
221 | ETH icon is displayed as [[image:1658135519305-444.png||height="18" width="19"]] Indicates that Ethernet is the main working network. | ||
222 | |||
223 | Cell icon is displayed as [[image:1658135500498-725.png||height="17" width="17"]] Indicates that Cellular is the backup WAN. | ||
224 | |||
225 | |||
226 | == 4.1 Switching between Cellular and Ethernet networks == | ||
227 | |||
228 | |||
229 | //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// | ||
230 | |||
231 | [[image:image-20220606140622-2.png||height="664" width="1106"]] | ||
232 | |||
233 | |||
234 | //**Remove the network cable from the WAN port on the gateway, the gateway will switch to a Cellular network.**// | ||
235 | |||
236 | [[image:image-20220606140859-4.png||height="687" width="1107"]] | ||
237 | |||
238 | (% style="display:none" %) (%%) | ||
239 | |||
240 | == 4.2 Switching between Cellular and WiFi networks == | ||
241 | |||
242 | |||
243 | (% class="wikigeneratedid" %) | ||
244 | //Enable **Cellular** and connect **WiFi** at the same time// | ||
245 | |||
246 | //WiFi icon is displayed as //[[image:1658135519305-444.png||height="23" width="24"]] Indicates that WiFi is the main working network. | ||
247 | |||
248 | //Cell icon is displayed as //[[image:1658135500498-725.png||height="23" width="22"]]// Indicates that Cellular is the backup WAN.// | ||
249 | |||
250 | |||
251 | [[image:image-20220606141113-7.png||height="678" width="1106"]] | ||
252 | |||
253 | |||
254 | //**Close the WiFi WAN, the gateway will switch to a Cellular network.**// | ||
255 | |||
256 | [[image:image-20220606140932-5.png||height="687" width="1107"]] | ||
257 | |||
258 | |||
259 | == 4.3 At the same time start Cellular and Ethernet and Wi-Fi networks == | ||
260 | |||
261 | |||
262 | [[image:image-20220606140328-1.png||height="682" width="1108"]] | ||
263 | |||
264 | |||
265 | ))) | ||
266 | |||
267 | = 5. How does the gateway view the International Mobile Equipment Identity (IMEI) = | ||
268 | |||
269 | |||
270 | Users can get the IMEI via Linux command, but you have to access the gateway CLI. | ||
271 | |||
272 | (% class="box infomessage" %) | ||
273 | ((( | ||
274 | **root@dragino-1b7c4c:~~# comgt -d /dev/ttyModemAT -s /etc/gcom/getimsi.gcom ** | ||
275 | ))) | ||
276 | |||
277 | [[image:image-20221027140604-1.png||height="330" width="707"]] | ||
278 | |||
279 | |||
280 | [[image:image-20221027151146-2.png||height="554" width="1000"]] | ||
281 | |||
282 | |||
283 | == **How does the gateway access the Quetel module directly (to send AT commands)** == | ||
284 | |||
285 | |||
286 | //Users can access the gateway CLI and run the minicom command to get the configuration interface.// | ||
287 | |||
288 | ((( | ||
289 | |||
290 | |||
291 | **//Enter the minicom command, then select the option ''serial port setup".//** | ||
292 | ))) | ||
293 | |||
294 | (% class="box infomessage" %) | ||
295 | ((( | ||
296 | **root@dragino-1ef9ac:~~# minicom -s** | ||
297 | ))) | ||
298 | |||
299 | [[image:image-20220527154132-6.png]] | ||
300 | |||
301 | |||
302 | And then, change the setting: | ||
303 | |||
304 | (% class="box infomessage" %) | ||
305 | ((( | ||
306 | **Serial Device :** (% style="color:#037691" %)**/dev/ttyModemAT** | ||
307 | |||
308 | **Bps/Par/Bits :(% style="color:#037691" %) 9600 8N1(%%)** | ||
309 | ))) | ||
310 | |||
311 | |||
312 | (% style="color:red" %)//**Note: Enter the corresponding letter to change the configuration, like A,B,C**// | ||
313 | |||
314 | [[image:image-20220527154154-7.png]] | ||
315 | |||
316 | |||
317 | === **International Mobile Equipment Identity (IMEI)** === | ||
318 | |||
319 | |||
320 | ((( | ||
321 | //Enter (% style="color:blue" %)**AT+GSN **(%%)in the interface to get the IMEI,// | ||
322 | ))) | ||
323 | |||
324 | ((( | ||
325 | //**For example: (% style="color:#037691" %)860548042566627(%%)**// | ||
326 | ))) | ||
327 | |||
328 | (% class="box infomessage" %) | ||
329 | ((( | ||
330 | ((( | ||
331 | **AT+GSN** | ||
332 | ))) | ||
333 | ))) | ||
334 | |||
335 | [[image:image-20220527154231-8.png]] | ||
336 | |||
337 | |||
338 | === **Integrated Circuit Card Identifier (ICCID)** === | ||
339 | |||
340 | |||
341 | ((( | ||
342 | //Enter (% style="color:blue" %)**AT+QCCID **(%%)in the interface to get the ICCID,// | ||
343 | ))) | ||
344 | |||
345 | ((( | ||
346 | //**For example: (% style="color:#037691" %)89860118005400261748(%%)**// | ||
347 | |||
348 | (% class="box infomessage" %) | ||
349 | ((( | ||
350 | **AT+QCCID** | ||
351 | ))) | ||
352 | ))) | ||
353 | |||
354 | [[image:1678675878256-777.png]] | ||
355 | |||
356 | |||
357 | = 6. How does the gateway connect to the network via a USB 4G Dongle = | ||
358 | |||
359 | == 6.1 Introduction == | ||
360 | |||
361 | |||
362 | (% style="color:red" %)**//Prerequisite: Requires a USB 4G Dongle and a supported gateway firmware//** | ||
363 | |||
364 | ((( | ||
365 | //This introduces a setup and configured gateway for using a USB 3g/UMTS-modem for WAN connection.// | ||
366 | |||
367 | |||
368 | ))) | ||
369 | |||
370 | ((( | ||
371 | //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.// | ||
372 | ))) | ||
373 | |||
374 | ((( | ||
375 | //This is not beginner-friendly due to too many protocols.// | ||
376 | |||
377 | //For more information: [[https:~~/~~/openwrt.org/docs/guide-user/network/wan/wwan/3gdongle>>url:https://openwrt.org/docs/guide-user/network/wan/wwan/3gdongle]]// | ||
378 | |||
379 | |||
380 | ))) | ||
381 | |||
382 | == 6.2 How to use the USB Dongle at the gateway == | ||
383 | |||
384 | |||
385 | //Most of the products can be used on the gateway, but because their protocols are different, they are not used in the same way.// | ||
386 | |||
387 | ((( | ||
388 | //For example, the Huawei-E3372/E8372 is using **Hilink mode** or **NCM mode**.// | ||
389 | ))) | ||
390 | |||
391 | (% class="box" %) | ||
392 | ((( | ||
393 | Huawei-E3372/E8372 | ||
394 | Check the (% style="color:#037691" %)**E3372**(% style="color:black" %) version to determine the mode. | ||
395 | The version numbers starting with 21 is NCM mode | ||
396 | The version numbers starting with 22 is Hilink mode | ||
397 | The E8372 only has Hilink mode | ||
398 | **~ **(% style="color:red" %)**Note: The e3372 in the vast majority of cases is Hilink mode** | ||
399 | ))) | ||
400 | |||
401 | |||
402 | == 6.3 Hilink mode == | ||
403 | |||
404 | |||
405 | //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/]]// | ||
406 | |||
407 | |||
408 | === 6.3.1 Plugs into the device === | ||
409 | |||
410 | |||
411 | ((( | ||
412 | //USB-Dongle plugs into the gateway USB port// | ||
413 | ))) | ||
414 | |||
415 | ((( | ||
416 | //Check the USB module via command (% style="color:#037691" %)**lsusb**// | ||
417 | ))) | ||
418 | |||
419 | ((( | ||
420 | (% style="color:red" %)//**Note: Users need to that connect to the gateway command line via ssh.**// | ||
421 | ))) | ||
422 | |||
423 | [[image:image-20220527154739-9.png]] | ||
424 | |||
425 | |||
426 | === 6.3.2 Detection of new network interfaces added === | ||
427 | |||
428 | |||
429 | //Check network configuration command line input: // | ||
430 | |||
431 | (% class="box infomessage" %) | ||
432 | ((( | ||
433 | ((( | ||
434 | **~ root@dragino-1ef9ac:~~# ifconfig -a** | ||
435 | ))) | ||
436 | ))) | ||
437 | |||
438 | [[image:image-20220527154822-10.png]] | ||
439 | |||
440 | //In the command, the output user can see that the new interface added is (% style="color:#037691" %)**eth2**// | ||
441 | |||
442 | //Usually, the user can see that the new interface added is (% style="color:#037691" %)**eth2** (% style="color:black" %)or (% style="color:#037691" %)**wwan0**// | ||
443 | |||
444 | |||
445 | === 6.3.3 Add the new interface to the network configuration. === | ||
446 | |||
447 | |||
448 | //Enter the configuration from the command line~:// | ||
449 | |||
450 | (% class="box" %) | ||
451 | ((( | ||
452 | uci set network.lte=interface | ||
453 | uci set network.lte.proto=dhcp | ||
454 | uci set network.lte.ifname=eth2 ~-~-~-~-~-~-~-~-->#This depend on the name of the new interface gateway add | ||
455 | uci commit network | ||
456 | uci set firewall.@zone[1].network="wan wwan wan6 lte" | ||
457 | uci commit firewall | ||
458 | /etc/init.d/network restart | ||
459 | ))) | ||
460 | |||
461 | [[image:image-20220527154937-11.png]] | ||
462 | |||
463 | |||
464 | //**Checking Network Configurations**// | ||
465 | |||
466 | //Command-line input: (% style="color:#037691" %)**ifconfig**// | ||
467 | |||
468 | [[image:image-20220527155013-12.png]] | ||
469 | |||
470 | //Now, Gateway is configured to access the internet on the LTE network.// | ||
471 | |||
472 | |||
473 | == 6.4 NCM mode == | ||
474 | |||
475 | |||
476 | == 6.5 Troubleshooting == | ||
477 | |||
478 | === 6.5.1 The USB-Dongle interface cannot obtain the IP address. === | ||
479 | |||
480 | |||
481 | //Please try this USB dongle to access the internet on your PC, to make sure this USB dongle can normally access the internet.// | ||
482 | |||
483 | |||
484 | = 7. How to reduce data traffic = | ||
485 | |||
486 | == 7.1 Reduce Status Uplink Interval == | ||
487 | |||
488 | |||
489 | **//The gateways will use the data traffic below two places.//** | ||
490 | |||
491 | |||
492 | //1. There is the data traffic from LoRa package Forward which were the gateway status package and sensor end node uplink/downlink.// | ||
493 | |||
494 | //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.// | ||
495 | |||
496 | [[image:image-20220527155108-13.png]] | ||
497 | |||
498 | |||
499 | |||
500 | //2. There is the data traffic from the gateway check self-network status. by default, the gateway will check the network per 15s.// | ||
501 | |||
502 | //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.// | ||
503 | |||
504 | [[image:image-20220527155358-16.png]] | ||
505 | |||
506 | //System General interface// | ||
507 | |||
508 | |||
509 | [[image:image-20220527155229-15.png]] | ||
510 | |||
511 | //Keepalive script interval time settings// | ||
512 | |||
513 | |||
514 | == 7.2 Filter unwanted packets == | ||
515 | |||
516 | |||
517 | See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]] | ||
518 | |||
519 | |||
520 | == 7.3 Usage statistics == | ||
521 | |||
522 | |||
523 | ~1. Activate LuCI and connect to SSH following [[these instructions>>doc:Main.Install Luci in the new UI firmware.WebHome]] | ||
524 | |||
525 | 2. Install luci-app-statistics using the following terminal commands: | ||
526 | |||
527 | {{{opkg update | ||
528 | opkg install luci-app-statistics | ||
529 | opkg install collectd-mod-interface | ||
530 | /etc/init.d/collectd enable | ||
531 | reboot | ||
532 | }}} | ||
533 | |||
534 | 3. Select the interface to be monitored by going to **Statistics > Setup **in the upper menu then **Network plugins > Interfaces. **Select **3g-cellular **in the list then save. You can select multiple interfaces by pressing the **ctrl key **while selecting the interfaces. | ||
535 | |||
536 | [[image:image-20221124133431-1.png]] | ||
537 | |||
538 | [[image:image-20221124135102-2.png]] | ||
539 | |||
540 | 4. View the graphs and statistics using by going to **Statistics > Graphs** **> Interfaces > 3g-cellullar** | ||
541 | |||
542 | [[image:image-20221124134927-1.png]] | ||
543 | |||
544 |