Changes between Version 26 and Version 27 of expansion/gw16126


Ignore:
Timestamp:
06/11/2019 07:44:20 PM (5 years ago)
Author:
Tim Harvey
Comment:

clean up examples

Legend:

Unmodified
Added
Removed
Modified

  • expansion/gw16126

    v26 v27  
    142142
    143143
    144 ==== Connection Examples ====
    145 4 different examples of how to connect, testing done on a Newport family board : (set APN env var appropriately)
    146  * Ubuntu using !NetworkManager:
    147 
    148 [[CollapsibleStart(Example)]]
     144==== Connection Examples
     145The following sections show connection examples for various Operating Environments:
     146 * [#nmcli NetworkManager]
     147 * [#mmcli ModemManager]
     148 * [#openwrt OpenWrt]
     149 * [#libqmi libqmi]
     150
     151[=#nmcli]
     152===== Network Manager (with !ModemManager and libqmi)
    149153{{{#!bash
    150154root@xenial-newport:~# nmcli --version
    … …  
    174178rtt min/avg/max/mdev = 188.688/378.624/568.561/189.937 ms
    175179}}}
    176 [[CollapsibleEnd]]
    177  * Ubuntu using !ModemManager:
    178 
    179 [[CollapsibleStart(Example)]]
     180
     181[=#mmcli]
     182===== !ModemManager (!No NetworkManager)
    180183{{{#!bash
    181184root@xenial-newport:~# mmcli --modem 0 #verify modem is detected
    … …  
    285288rtt min/avg/max/mdev = 188.688/378.624/568.561/189.937 ms
    286289}}}
    287 [[CollapsibleEnd]]
    288  * Ubuntu using libqmi only (no !NetworkManager or !ModemManager)
    289 [[CollapsibleStart(Example)]]
     290
     291[=#qmicli]
     292===== libqmi (no !NetworkManager or !ModemManager)
    290293{{{#!bash
    291294root@xenial-newport:~# qmicli --version
    … …  
    344347root@xenial-newport:~# echo "nameserver 198.224.182.135" > /etc/resolv.conf # assign nameserver
    345348}}}
    346 [[CollapsibleEnd]]
    347 
    348  * !OpenWrt (18.06)
    349   * !OpenWrt will auto-configure the modem once the following is added to the /etc/config/network file (change APN as appropriate)
     349
     350[=#openwrt]
     351===== OpenWrt
     352Note that OpenWrt 18.06 or newer has support for this modem.
    350353{{{#!bash
    351354config interface 'wan'
    … …  
    358361}}}
    359362
    360  * Troubleshooting (requires qmicli and stopping ModemManager: systemctl stop ModemManager)
    361   * Check system info. Note below the 'True Status' states 'limited-regional'. That usually means the device is registered for emergency services only. This has nothing to do with APN being wrong, it still needs a "full" proper LTE registration before you try with the APNs. Try to talk to Verizon/Provider support about the status of this account and see what they say.
    362 {{{
     363
     364==== Troubleshooting
     365General Notes:
     366 * if not using PPP make sure you have the latest firmware for proper QMI support - contact support@gateworks.com
     367 * You must be 'registered' on a provider network before you can connect. This registration occurs based on SIM, IMEI, and Mobile Network Operator selection.
     368
     369Refer to [wiki:wireless/modem#libqmi wireless/modem/libqmi] commands for general troubleshooting using libqmi.
     370
     371Some troubleshooting using qmicli:
     372 * Stop !ModemManager if it is running
     373 * Check registration:
     374{{{#!bash
     375root@ventana:~# qmicli -d /dev/cdc-wdm0 --nas-get-serving-system
     376[/dev/cdc-wdm0] Successfully got serving system:
     377        Registration state: 'registered'
     378        CS: 'detached'
     379        PS: 'attached'
     380        Selected network: '3gpp'
     381        Radio interfaces: '1'
     382                [0]: 'lte'
     383        Roaming status: 'off'
     384        Data service capabilities: '1'
     385                [0]: 'lte'
     386        Current PLMN:
     387                MCC: '311'
     388                MNC: '480'
     389                Description: 'VZW'
     390        Roaming indicators: '1'
     391                [0]: 'off' (lte)
     392        3GPP location area code: '65534'
     393        3GPP cell ID: '8550402'
     394        Detailed status:
     395                Status: 'available'
     396                Capability: 'ps'
     397                HDR Status: 'none'
     398                HDR Hybrid: 'no'
     399                Forbidden: 'no'
     400        LTE tracking area code: '8450'
     401        Full operator code info:
     402                MCC: '311'
     403                MNC: '480'
     404                MNC with PCS digit: 'yes'
     405}}}
     406  - Note {{{Registration state: 'registered'}}} above indicating you are registered and 'Current PLMN' of VZW indicating you are registered with Verizon
     407 * Check system info:
     408{{{#!bash
    363409root@bionic-armhf:~# qmicli -d /dev/cdc-wdm0 --nas-get-system-info
    364410[/dev/cdc-wdm0] Successfully got system info:
    … …  
    375421        SIM reject info: 'available'
    376422}}}
    377   * Get home network information
    378 {{{
     423  - Note above the 'True Status' states 'limited-regional'. That usually means the device is registered for emergency services only. This must occur before you can 'connect' using an APN (thus has nothing to do with the APN being wrong). Refer to your Provider if you have difficulty getting registered on the network.
     424 * Get home network information
     425{{{#!bash
    379426root@bionic-armhf:~# qmicli -d /dev/cdc-wdm0 --nas-get-home-network
    380427[/dev/cdc-wdm0] Successfully got home network:
    … …  
    385432
    386433}}}
    387   * Get signal info
     434 * Get signal info
    388435{{{
    389436root@bionic-armhf:~# qmicli -d /dev/cdc-wdm0 --nas-get-signal-info
    … …  
    395442        SNR: '19.8 dB'
    396443}}}
    397   * Get signal strength
     444 * Get signal strength
    398445{{{
    399446root@bionic-armhf:~# qmicli -d /dev/cdc-wdm0 --nas-get-signal-strength
    … …  
    415462
    416463}}}
    417 
    418   * Get serving system
     464 * Get serving system
    419465{{{
    420466root@bionic-armhf:~# qmicli -d /dev/cdc-wdm0 --nas-get-serving-system
    … …  
    443489}}}
    444490
     491Note that all of the above has to be good before you can obtain a data connection with your provider via the 'qmi-network start' command which is the step that requires a proper APN that your provider supports.
    445492
    446493[=#nina-b3]