MC7354 with Verizon network

Mon Jan 23 22:02:30 UTC 2017

Thanks Tang

But I didnt want to connect with the ipv6
i just need ipv4 address


Thanks

2017-01-23 22:55 GMT+01:00 Tang Nguyen <tang_nguyen at yahoo.com>:

> It doesn't work because APN of PDP#3 is different with the APN that you
> want to connect to network.
>
> Issue below command to get correct APN, which associates with your SIM
> card, and pass that APN to "qmicli connect" command.
>
> qmicli -d /dev/cdc-wdm0 --wds-get-default-settings=3gpp
>
>
> PS. You can use command: AT+CGPIAF=1 to show correct IPv6 format from
> AT+CGCINTRDP command
>
>
> --tang
>
> --------------------------------------------
> On Mon, 1/23/17, heni wael <waelheni91 at gmail.com> wrote:
>
>  Subject: Re: MC7354 with Verizon network
>  To: "Sebastian Sjoholm" <sebastian.sjoholm at gmail.com>,
> libqmi-devel at lists.freedesktop.org
>  Date: Monday, January 23, 2017, 4:34 PM
>
>  OK
>  now i have firmware installed and the
>  network connected
>  i try to use
>  qmicli to do the LTE connection
>  i have
>  this
>
>  AT
>  OK
>  AT!ENTERCND="A710"
>  OK
>  AT!UDUSBCOMP?
>  !UDUSBCOMP: 6
>
>  OK
>  AT!GOBIIMPREF
>  ERROR
>  AT!GOBIIMPREF?
>  !GOBIIMPREF:
>   preferred fw
>  version:   05.05.58.01
>   preferred carrier
>  name: VZW
>   preferred config name:
>  VZW_005.029_000
>   current fw
>  version:     05.05.58.01
>   current
>  carrier name:   VZW
>   current config
>  name:    VZW_005.029_000
>
>  OK
>
>
>  And network connected
>  i dont know if the PDP is Ok  or not
>
>
>  AT
>  OK
>  at!gstatus?
>  !GSTATUS:
>  Current Time:
>  203              Temperature: 33
>  Bootup Time:
>  5                Mode:
>  ONLINE
>  System mode:
>  LTE              PS state:
>  Attached
>  LTE band:
>  B4               LTE bw:      10 MHz
>
>  LTE Rx chan:
>  2100             LTE Tx chan: 20100
>  EMM state:     Registered
>  Normal Service
>  RRC state:     RRC
>  Idle
>  IMS reg state: Full
>  Srv         IMS mode:    Normal
>
>  RSSI (dBm):
>  -54              Tx Power:    0
>  RSRP (dBm):    -78
>  TAC:         2501 (9473)
>  RSRQ
>  (dB):     -9               Cell
>  ID:     0091A216 (9544214)
>  SINR
>  (dB):      3.6
>
>
>  OK
>  AT+CGCONTRDP
>  +CGCONTRDP:
>  1,5,vzwims,38.0.16.16.129.83.54.223.0.0.0.23.143.19.114.1,
>  254.128.0.0.0.0.0.0.0.0.0.23.143.19.114.64,
>  32.1.72.136.0.104.6
>
>  OK
>  AT+CGDCONT?
>  +CGDCONT:
>  1,"IPV4V6","vzwims","0.0.0.0",0,0
>  +CGDCONT:
>  2,"IPV4V6","vzwadmin","0.0.0.0",0,0
>  +CGDCONT:
>  3,"IPV4V6","vzwinternet","0.0.0.0",0,0
>  +CGDCONT:
>  4,"IPV4V6","vzwapp","0.0.0.0",0,0
>  +CGDCONT:
>  5,"IPV4V6","vzw800","0.0.0.0",0,0
>  +CGDCONT:
>  9,"IPV6","vzwims","0.0.0.0",0,0
>  +CGDCONT:
>  10,"IP","vzwadmin","0.0.0.0",0,0
>  +CGDCONT:
>  11,"IP","vzwinternet","0.0.0.0",0,0
>  +CGDCONT:
>  12,"IPV4V6","vzwapp","0.0.0.0",0,0
>  +CGDCONT:
>  13,"IP","","0.0.0.0",0,0
>
>  OK
>  AT+CGATT?
>  +CGATT: 1
>
>  OK
>
>  but when i try to use the qmicli i got an
>  error
>
>
>  [root at localhost ~]# qmi-network  /dev/cdc-wdm0
>  start
>  Loading profile at
>  /etc/qmi-network.conf...
>      APN:
>  we01.vzwstatic
>      APN user: unset
>      APN password: unset
>      qmi-proxy: no
>  Loading
>  previous state from /tmp/qmi-network-state-cdc-wdm0...
>      Previous CID: 1
>
>  Previous PDH: 1138072296
>  error: cannot
>  re-start network, PDH already exists
>
>  qmicli -d /dev/cdc-wdm0
>  --wds-get-current-settings
>  [root at localhost
>  ~]# qmicli -d /dev/cdc-wdm0 --wds-get-current-settings
>  error: couldn't get current settings: QMI
>  protocol error (15): 'OutOfCall'
>  [root at localhost ~]# qmi-network  /dev/cdc-wdm0
>  start
>  Loading profile at
>  /etc/qmi-network.conf...
>      APN:
>  we01.vzwstatic
>      APN user: unset
>      APN password: unset
>      qmi-proxy: no
>  Loading
>  previous state from /tmp/qmi-network-state-cdc-wdm0...
>      Previous CID: 1
>
>  Previous PDH: 1138072296
>  error: cannot
>  re-start network, PDH already exists
>
>  have you got an idea ?
>
>  2017-01-23 21:35 GMT+01:00
>  heni wael <waelheni91 at gmail.com>:
>  Ok Thanks
>
>
>  2017-01-23 21:31 GMT+01:00
>  Sebastian Sjoholm <sebastian.sjoholm at gmail.com>:
>  > On Jan 23, 2017, at
>  21:26 , heni wael <waelheni91 at gmail.com>
>  wrote:
>
>  >
>
>  > [root at localhost ~]# cat /etc/modprobe.d/blacklist-mode
>  m.conf
>
>  > blacklist qcserial
>
>  > blacklist qmi_wwan
>
>  > blacklist usb_wwan
>
>  > blacklist cdc_mbim
>
>  > blacklist cdc_wdm
>
>  > blacklist cdc_ncm
>
>  > blacklist sierra
>
>  > blacklist sierra_net
>
>  > [root at localhost ~]#
>
>  >
>
>
>
>  That looks pretty OK, and the dmesg and lsusb -t
>  shows that the qmi_wwan is still loaded after that?
>
>
>
>  I can find a bunch of cases via google when the blacklist
>  file is not loaded, but it is depended on what linux you are
>  running, I think a google search for your system would be a
>  good start.
>
>
>
>  -Sebastian
>
>
>
>
>
>
>
>
>
>
>
>  -----Inline Attachment Follows-----
>
>  _______________________________________________
>  libqmi-devel mailing list
>  libqmi-devel at lists.freedesktop.org
>  https://lists.freedesktop.org/mailman/listinfo/libqmi-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libqmi-devel/attachments/20170123/90e915f6/attachment.html>