MC7455 Raspberry pi - ping command doesn't work

Hello all!
I build the os for Raspberry using yocto and I’m using qmicli to connect the module, but when I run the ping command it’s looks like I don’t have an internet connection, I don’t if I’m missing a configuration or what I’m doing wrong, Does any help me whit this? I will appreciate your comments and support! Thanks!!

Logs:

MODEM:

at+gmrR
SWI9X30C_02.08.02.00 r5428 CARMD-EV-FRMWR2 2016/01/06 20:38:53

OS Info and Lib version

root@raspberrypi3:~# uname -a
Linux raspberrypi3 5.4.72-v7 #1 SMP Sun Nov 15 00:27:21 UTC 2020 armv7l GNU/Linux

root@raspberrypi3:~# qmicli --version

qmicli 1.24.12
Copyright (C) 2012-2019 Aleksander Morgado
License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

##### Configuration #####

    root@raspberrypi3:~# ifconfig wwan0 down

    root@raspberrypi3:~# qmicli -d /dev/cdc-wdm0 --set-expected-data-format=raw-ip
    [/dev/cdc-wdm0] expected data format set to: raw-ip

    root@raspberrypi3:~# qmicli -d /dev/cdc-wdm0 --device-open-proxy --wda-get-data-format
    [/dev/cdc-wdm0] Successfully got data format
                       QoS flow header: no
                   Link layer protocol: 'raw-ip'
      Uplink data aggregation protocol: 'disabled'
    Downlink data aggregation protocol: 'disabled'
                         NDP signature: '0'
    Downlink data aggregation max datagrams: '0'
    Downlink data aggregation max size: '0'

    root@raspberrypi3:~# ifconfig wwan0 up

    root@raspberrypi3:~# qmicli -d /dev/cdc-wdm0 --device-open-net="net-raw-ip|net-no-qos-header" --wds-start-network=web.iusacellgsm.mx --client-n
    o-release-cid
    [/dev/cdc-wdm0] Network started
            Packet data handle: '62938192'
    [/dev/cdc-wdm0] Client ID not released:
            Service: 'wds'
                CID: '35'

    root@raspberrypi3:~# udhcpc -i wwan0
    udhcpc: started, v1.31.1
    udhcpc: sending discover
    udhcpc: sending select for 100.98.70.193
    udhcpc: lease of 100.98.70.193 obtained, lease time 7200
    /etc/udhcpc.d/50default: Adding DNS 201.175.154.44
    /etc/udhcpc.d/50default: Adding DNS 201.175.154.45

    root@raspberrypi3:~# route -n
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    0.0.0.0         100.98.70.194   0.0.0.0         UG    10     0        0 wwan0
    100.98.70.192   0.0.0.0         255.255.255.252 U     0      0        0 wwan0

    root@raspberrypi3:~# ping -I wwan0 google.com
    PING google.com (216.58.193.4): 56 data bytes   <-- it is stock here.
    ^Z[1]+  Stopped                    ping -I wwan0 www.google.com

    root@raspberrypi3:~# qmicli -d /dev/cdc-wdm0 --wds-get-current-settings
    [/dev/cdc-wdm0] Current settings retrieved:
               IP Family: IPv4
            IPv4 address: 100.98.70.193
        IPv4 subnet mask: 255.255.255.252
    IPv4 gateway address: 100.98.70.194
        IPv4 primary DNS: 201.175.154.44
      IPv4 secondary DNS: 201.175.154.45
                     MTU: 1500
                 Domains: none

    root@raspberrypi3:~# ifconfig 
    eth0      Link encap:Ethernet  HWaddr B8:27:EB:32:06:49  
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

    lo        Link encap:Local Loopback  
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:65536  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

    wwan0     Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
              inet addr:100.98.70.193  P-t-P:100.98.70.193  Mask:255.255.255.252
              inet6 addr: fe80::b41e:32c6:8dda:fa0a/64 Scope:Link
              UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
              RX packets:30 errors:0 dropped:0 overruns:0 frame:0
              TX packets:115 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:9892 (9.6 KiB)  TX bytes:8772 (8.5 KiB)

    root@raspberrypi3:~# cat /etc/network/interfaces 
    # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
    # The loopback interface

    auto lo
    iface lo inet loopback

    # Wired or wireless interfaces
    auto eth0
    iface eth0 inet static
            address 192.168.1.2
            netmask 255.255.255.0
            gateway 192.168.1.1
            network 192.168.1.0

    #cellular adapter
    auto wwan0
    allow-hotplug wwan0

    root@raspberrypi3:~# cat /etc/resolv.conf 
    # This file is managed by man:systemd-resolved(8). Do not edit.
    #
    # This is a dynamic resolv.conf file for connecting local clients directly to
    # all known uplink DNS servers. This file lists all configured search domains.
    #
    # Third party programs must not access this file directly, but only through the
    # symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
    # replace this symlink by a static file or a different symlink.
    #
    # See man:systemd-resolved.service(8) for details about the supported modes of
    # operation for /etc/resolv.conf.

    nameserver 201.175.154.44
    nameserver 201.175.154.45

Hi jesusp

Please use SDK and driver officially from Sierra Wireless.
You can use the Connection_manager sample in SDK to establish the data connection.

You can get them here Linux QMI SDK Software
Linux QMI Driver

@jesusp

We do recommend using the Sierra drivers but the unit should work with the open source ones happily (we have a lot of customers using them in various systems).

So given the interface is fully populated and it looks like you have started a session what does a
ping -I wwan0 8.8.8.8

return? All looks fine to me.

Regards

Matt

1 Like

SWI9X30C_02.08.02.00 r5428 CARMD-EV-FRMWR2 2016/01/06 20:38:53

For MC7455, FW 02.08.02 is too old. It would be better to use the latest one posted here(02.33.03/02.32.11).

https://source.sierrawireless.com/resources/airprime/minicard/74xx/airprime-em_mc74xx-approved-fw-packages/#sthash.djpBP7sb.dpbs

1 Like

Hi Matt at the end was the SIM activation, my mistake LoL, I activated the SIM with my provider and now all works fine, thanks for assistance me, I will take a look to update the firmware in my cellular module. Happy new year!