• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Register
  • Login
ModalAI Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
    • Register
    • Login

    LTE - Modem Works But Cannot Ping

    Cellular Modems
    4
    27
    2.5k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      tom admin
      last edited by 18 Aug 2021, 22:51

      @derrick0799 Do you have WiFi connected? If so, try disabling it with ifconfig wlan0 down and seeing if you can then ping.

      Also, can I see the output of route -n?

      Same for you @vmassague something to try.

      D 1 Reply Last reply 18 Aug 2021, 23:05 Reply Quote 0
      • T
        tom admin @derrick0799
        last edited by 18 Aug 2021, 22:51

        @derrick0799 Looks like APN is setting correctly so that's good

        1 Reply Last reply Reply Quote 0
        • D
          derrick0799 @tom
          last edited by 18 Aug 2021, 23:05

          @tom after disabling wlan0,
          / # ping 8.8.8.8
          connect: Network is unreachable

          / # route -n
          Kernel IP routing table
          Destination Gateway Genmask Flags Metric Ref Use Iface
          172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
          / #

          1 Reply Last reply Reply Quote 0
          • T
            tom admin
            last edited by 18 Aug 2021, 23:07

            @derrick0799 What does ifconfig show?

            D 1 Reply Last reply 18 Aug 2021, 23:08 Reply Quote 0
            • D
              derrick0799 @tom
              last edited by 18 Aug 2021, 23:08

              @tom
              / # ifconfig
              docker0 Link encap:Ethernet HWaddr 02:42:77:DF:4E:80
              inet addr:172.17.0.1 Bcast:0.0.0.0 Mask:255.255.0.0
              inet6 addr: fe80::42:77ff:fedf:4e80/64 Scope:Link
              UP BROADCAST MULTICAST MTU:1500 Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:0 (0.0 B) TX bytes:140 (140.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:609376 errors:0 dropped:0 overruns:0 frame:0
              TX packets:609376 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:65142775 (62.1 MiB) TX bytes:65142775 (62.1 MiB)

              / #

              1 Reply Last reply Reply Quote 0
              • T
                tom admin
                last edited by 18 Aug 2021, 23:24

                @derrick0799 Is that the output after running voxl-modem-start.sh?

                1 Reply Last reply Reply Quote 0
                • T
                  tom admin
                  last edited by 18 Aug 2021, 23:28

                  At that point, you should be seeing something similar to:

                  wwan0     Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
                            inet addr:30.60.23.115  P-t-P:30.60.23.115  Mask:255.255.255.248
                            UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
                            RX packets:33 errors:0 dropped:0 overruns:0 frame:0
                            TX packets:55 errors:0 dropped:0 overruns:0 carrier:0
                            collisions:0 txqueuelen:1000 
                            RX bytes:3214 (3.1 KiB)  TX bytes:4672 (4.5 KiB)
                  
                  D 2 Replies Last reply 18 Aug 2021, 23:32 Reply Quote 0
                  • D
                    derrick0799 @tom
                    last edited by 18 Aug 2021, 23:32

                    @tom I think my problem was that the wifi was connected when I ran the voxl-modem-start.sh
                    Now that I am connect with adb everything started working when I re-ran voxl-modem-start.sh. It is pinging as it should.

                    1 Reply Last reply Reply Quote 0
                    • D
                      derrick0799 @tom
                      last edited by 18 Aug 2021, 23:35

                      @tom
                      / # ifconfig
                      docker0 Link encap:Ethernet HWaddr 02:42:77:DF:4E:80
                      inet addr:172.17.0.1 Bcast:0.0.0.0 Mask:255.255.0.0
                      inet6 addr: fe80::42:77ff:fedf:4e80/64 Scope:Link
                      UP BROADCAST MULTICAST MTU:1500 Metric:1
                      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
                      TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
                      collisions:0 txqueuelen:0
                      RX bytes:0 (0.0 B) TX bytes:140 (140.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:1472332 errors:0 dropped:0 overruns:0 frame:0
                      TX packets:1472332 errors:0 dropped:0 overruns:0 carrier:0
                      collisions:0 txqueuelen:0
                      RX bytes:155328799 (148.1 MiB) TX bytes:155328799 (148.1 MiB)

                      wwan0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
                      inet addr:100.76.95.21 P-t-P:100.76.95.21 Mask:255.255.255.252
                      UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
                      RX packets:2 errors:0 dropped:0 overruns:0 frame:0
                      TX packets:2713 errors:0 dropped:0 overruns:0 carrier:0
                      collisions:0 txqueuelen:1000
                      RX bytes:612 (612.0 B) TX bytes:1304344 (1.2 MiB)

                      / # ping 8.8.8.8
                      PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
                      64 bytes from 8.8.8.8: icmp_req=1 ttl=113 time=34.3 ms
                      64 bytes from 8.8.8.8: icmp_req=2 ttl=113 time=35.1 ms
                      64 bytes from 8.8.8.8: icmp_req=3 ttl=113 time=34.0 ms
                      64 bytes from 8.8.8.8: icmp_req=4 ttl=113 time=27.1 ms
                      64 bytes from 8.8.8.8: icmp_req=5 ttl=113 time=31.1 ms
                      64 bytes from 8.8.8.8: icmp_req=6 ttl=113 time=36.5 ms
                      64 bytes from 8.8.8.8: icmp_req=7 ttl=113 time=24.0 ms

                      Thanks @Tom

                      1 Reply Last reply Reply Quote 0
                      • T
                        tom admin
                        last edited by 18 Aug 2021, 23:36

                        @derrick0799 Great to hear!

                        1 Reply Last reply Reply Quote 0
                        • V
                          vmassague
                          last edited by 19 Aug 2021, 08:15

                          Problem solved for me too! I think it was also the wlan0 being up. Thanks a lot for the support @tom

                          T 1 Reply Last reply 20 Aug 2021, 17:51 Reply Quote 0
                          • T
                            tom admin @vmassague
                            last edited by 20 Aug 2021, 17:51

                            @vmassague Awesome!

                            1 Reply Last reply Reply Quote 0
                            • wilkinsafW wilkinsaf referenced this topic on 21 Jun 2023, 02:46
                            16 out of 27
                            • First post
                              16/27
                              Last post
                            Powered by NodeBB | Contributors