All geek questions in one place

Cannot start adb ping host application

Now I want to check whether an Android device can connect to another device via a network. I can use a browser to access the Internet. But when I use adb shell to connect to android emulator and use ping command to connect to host, it fails.

 kaiwii@ubuntu :~$ adb shell ping 192.168.145.136 PING 192.168.145.136 (192.168.145.136) 56(84) bytes of data. ^C

(192.168.145.136 - host ip!)

But when I pin 127.0.0.1, it works. Therefore, I am sure that the device supports the ping command. I am just confused why it cannot ping a host while I can access the Internet in a browser. What else, can anyone show any other method of testing network capability in android?

thanks

+4
source share
2 answers

You are connected to the Internet using a data connection by phone, and not via USB through the host computer. Thus, there is no network connection between your device and the host. In addition, since your host does not have a public IP address (it is behind multiple NAT levels, at least one level obvious from the IP address), it is not possible for the device to ping your host over the public Internet.

As for checking network connectivity, you can try the following:

  • ping www.google.com

Exit:

  / $ ping -c1 www.google.com PING www.google.com (74.125.236.51) 56(84) bytes of data. 64 bytes from www.google.com (74.125.236.51): icmp_seq=1 ttl=55 time=40.8 ms 64 bytes from www.google.com (74.125.236.51): icmp_seq=2 ttl=55 time=47.1 ms --- www.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 40.850/43.999/47.148/3.149 ms
  • check network connections: busybox ifconfig -a

Output (slightly reducing it):

 eth0 Link encap:Ethernet HWaddr 5C:4C:A9:FC:B0:C0 inet addr:192.168.2.3 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::5e4c:a9ff:fefc:b0c0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:359 errors:0 dropped:0 overruns:0 frame:0 TX packets:275 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:87543 (85.4 KiB) TX bytes:48382 (47.2 KiB) 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:16436 Metric:1 RX packets:620 errors:0 dropped:0 overruns:0 frame:0 TX packets:620 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:74037 (72.3 KiB) TX bytes:74037 (72.3 KiB) rmnet0 Link encap:Ethernet HWaddr 9E:43:B5:97:81:B1 inet addr:106.197.224.94 Bcast:106.197.224.95 Mask:255.255.255.252 BROADCAST MULTICAST MTU:2000 Metric:1 RX packets:54337 errors:0 dropped:0 overruns:0 frame:0 TX packets:59160 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:32720935 (31.2 MiB) TX bytes:8334589 (7.9 MiB) <snipped value="rmnet1,rmnet2" /> sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 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:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) <snipped value="tunl0,usb0" />
  • A faithful browser and Google combo.
+2
source

adb shell ping -c1 www.google.com

will return below the answer if the device has internet

  PING www.google.com (xx.xx.xx.xx) 56(84) bytes of data. 64 bytes from (xx.xx.xx.xx): icmp_seq=1 ttl=61 time=25.3 ms --- www.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 25.332/25.332/25.332/0.000 ms

or more

 ping: unknown host www.google.com
+1
source

Source: https://habr.com/ru/post/1414293/

More articles:


All Articles