In general, I ask you to treat my question with condescensions because I am not a programmer (and not when, I was not an excellent student).
In general, I have a device in which Linux Debian 9 is installed. This operating system is specific and compiled for a device, for example, there is no X11 graphical interface in it.
The system itself works perfectly under the SSH protocol, and the /etc/ directory has the /etc/network folder and the networks document is filled as expected (compared with the resbian from which I write this question on the Internet) in the file /ect/resolv.conf is still repeats. But when in the command line I enter ping www.ru then it gives me ping: www.ru: Temporary failure in name resolution
The essence of the question: I can not understand what utilities are missing. If not to lazy, how to install: 3 As you might guess, the sudo apt-get имя_утилиты does not work, and therefore the standard web-based offer simply does not work.
Here is added:
Here I called ip addr , dhclient eth0 , ping 8.8.8.8
Here she called from rasberi on the same wire ip addr , dhclient eth0 , ping 8.8.8.8
pi@raspberrypi:~ $ ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether b8:27:eb:5b:bb:57 brd ff:ff:ff:ff:ff:ff inet 172.16.8.166/24 brd 172.16.8.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::3ce0:5e8:71c9:b5ec/64 scope link valid_lft forever preferred_lft forever 3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether b8:27:eb:0e:ee:02 brd ff:ff:ff:ff:ff:ff pi@raspberrypi:~ $ dhclient eth0 RTNETLINK answers: Operation not permitted pi@raspberrypi:~ $ 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_seq=1 ttl=119 time=2.33 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=2.19 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=2.29 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=119 time=2.19 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=119 time=2.20 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=119 time=2.12 ms 64 bytes from 8.8.8.8: icmp_seq=7 ttl=119 time=2.19 ms 64 bytes from 8.8.8.8: icmp_seq=8 ttl=119 time=2.17 ms 64 bytes from 8.8.8.8: icmp_seq=9 ttl=119 time=2.21 ms 64 bytes from 8.8.8.8: icmp_seq=10 ttl=119 time=2.22 ms 64 bytes from 8.8.8.8: icmp_seq=11 ttl=119 time=2.22 ms 64 bytes from 8.8.8.8: icmp_seq=12 ttl=119 time=2.17 ms ^Z [6]+ Остановлен ping 8.8.8.8 
I communicate with the device using the COM port.
when I enter ifconfig
pi@raspberrypi:~ $ ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.16.8.166 netmask 255.255.255.0 broadcast 172.16.8.255 inet6 fe80::3ce0:5e8:71c9:b5ec prefixlen 64 scopeid 0x20<link> ether b8:27:eb:5b:bb:57 txqueuelen 1000 (Ethernet) RX packets 156437 bytes 107321282 (102.3 MiB) RX errors 0 dropped 1327 overruns 0 frame 0 TX packets 53377 bytes 6674202 (6.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 2 bytes 78 (78.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2 bytes 78 (78.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether b8:27:eb:0e:ee:02 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 when on the device I enter ifconfig
Ifconfig or ip a list and compare the details with those that show "Windows" when the cable is peredakaete. - @nobody
Here is Windows 7
here is debian 9
