M7354 IPv6 Problem

[Aleksander Morgado]

Hey,

Have you checked this libqmi thread?
http://lists.freedesktop.org/archives/libqmi-devel/2014-December/001036.html

There are some good comments there from Bjørn regarding default
profiles and the ipv4-or-ipv6 context.

Also, see some clarifications below about how to use qmicli along with
ModemManager, unrelated to your issue.

>
> root at router:/home# mmcli -L
>
> Found 1 modems:
>     /org/freedesktop/ModemManager1/Modem/0 [Sierra Wireless, Incorporated]
> MC7354
>
> root at router:/home# mmcli -m 0
>
> /org/freedesktop/ModemManager1/Modem/0 (device id
> '08fd8263ec2eb5f680a533bdcded55eef628d7bb')
>   -------------------------
>   Hardware |   manufacturer: 'Sierra Wireless, Incorporated'
>            |          model: 'MC7354'
>            |       revision: 'SWI9X15C_05.05.16.03 r22385 carmd-fwbuild1
> 2014/06/04 15:01:26'
>            |      supported: 'gsm-umts
>            |                  cdma-evdo
>            |                  lte
>            |                  cdma-evdo, gsm-umts
>            |                  gsm-umts, lte
>            |                  cdma-evdo, lte
>            |                  cdma-evdo, gsm-umts, lte'
>            |        current: 'lte'
>            |   equipment id: '359225052167129'
>   -------------------------
>   System   |         device: '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1'
>            |        drivers: 'qmi_wwan, option1'
>            |         plugin: 'Generic'
>            |   primary port: 'cdc-wdm2'
>            |          ports: 'ttyUSB0 (qcdm), ttyUSB2 (at), wwan0 (net),
> wwan1 (net), cdc-wdm2 (qmi), cdc-wdm1 (qmi)'
>   -------------------------
>   Numbers  |           own : '2019196694'
>   -------------------------
>   Status   |           lock: 'sim-pin2'
>            | unlock retries: 'sim-pin (3), sim-pin2 (3), sim-puk (10),
> sim-puk2 (10)'
>            |          state: 'disabled'
>            |    power state: 'on'
>            |    access tech: 'unknown'
>            | signal quality: '0' (cached)
>   -------------------------
>   Modes    |      supported: 'allowed: 4g; preferred: none'
>            |        current: 'allowed: 4g; preferred: none'
>   -------------------------
>   Bands    |      supported: 'cdma-bc0-cellular-800, cdma-bc1-pcs-1900,
> cdma-bc10-secondary-800, cdma-bc15-aws, dcs, egsm, pcs, g850, u2100, u1900,
> u17iv, u850, u900, eutran-ii, eutran-iv, eutran-v, eutran-xiii, eutran-xvii,
> eutran-xxv'
>            |        current: 'cdma-bc0-cellular-800, cdma-bc1-pcs-1900,
> cdma-bc15-aws, dcs, egsm, pcs, g850, u2100, u1900, u850, u900, eutran-iv,
> eutran-xiii'
>   -------------------------
>   IP       |      supported: 'ipv4, ipv6, ipv4v6'
>   -------------------------
>   3GPP     |           imei: '359225052167129'
>            |  enabled locks: 'none'
>            |    operator id: 'unknown'
>            |  operator name: 'unknown'
>            |   registration: 'unknown'
>   -------------------------
>   SIM      |           path: '/org/freedesktop/ModemManager1/SIM/0'
>
>
> root at router:/home# qmicli -d /dev/cdc-wdm2 --wds-get-profile-list=3gpp
> [24 Sep 2015, 11:09:46] -Warning ** Error reading from istream: Resource
> temporarily unavailable
> ^Ccancelling the operation...
>
> error: couldn't create client for the 'wds' service: CID allocation failed
> in the CTL client: Transaction aborted

You shouldn't try to run any QMI command directly in the same
/dev/cdc-wdm port which is using ModemManager (see "primary port"
reported above). If you do want to do that, you'll need to add the
extra "--device-open-proxy" option to your qmicli command (or shorter,
"-p"). See https://sigquit.wordpress.com/2013/09/13/sharing-a-qmi-port-between-processes/

> root at router:/home/m2m# qmicli -d /dev/cdc-wdm1 --wds-get-profile-list=3gpp
> Profile list retrieved:
>     [1] 3gpp - profile1
>         APN: 'INTERNET'
>         PDP type: 'ipv4-or-ipv6'
>         Auth: 'none'
>     [2] 3gpp - profile2
>         APN: 'admin'
>         PDP type: 'ipv4-or-ipv6'
>         Auth: 'none'
>     [3] 3gpp - profile3
>         APN: 'INTERNET'
>         PDP type: 'ipv4-or-ipv6'
>         Auth: 'none'
>     [4] 3gpp - profile4
>         APN: 'app'
>         PDP type: 'ipv4-or-ipv6'
>         Auth: 'none'
>     [5] 3gpp - profile5
>         APN: '800'
>         PDP type: 'ipv4-or-ipv6'
>         Auth: 'none'
>     [9] 3gpp - profile9
>         APN: 'ims'
>         PDP type: 'ipv6'
>         Auth: 'none'
>     [10] 3gpp - profile10
>         APN: 'admin'
>         PDP type: 'ipv4'
>         Auth: 'none'
>     [11] 3gpp - profile11
>         APN: 'INTERNET'
>         PDP type: 'ipv4'
>         Auth: 'none'
>     [12] 3gpp - profile12
>         APN: 'app'
>         PDP type: 'ipv4-or-ipv6'
>         Auth: 'none'
>     [13] 3gpp - profile13
>         PDP type: 'ipv4'
>         Auth: 'none'

In this case it worked without the "--device-open-proxy" option
because /dev/cdc-wdm1 wasn't being used by ModemManager.

-- 
Aleksander
https://aleksander.es