# Destination host unreacheble

**URL:** <https://www.debian-fr.org/t/destination-host-unreacheble/81560>\
**Category:** Support Debian\
**Created:** [Mars 21, 2020, 10:30 UTC](https://www.debian-fr.org/t/destination-host-unreacheble/81560 "2020-03-21T10:30:33Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Koneke](https://www.debian-fr.org/user_avatar/www.debian-fr.org/koneke/32/9022_2.png) [@Koneke](https://www.debian-fr.org/u/Koneke)\
**Post date:** [Mars 21, 2020, 10:30 UTC](https://www.debian-fr.org/t/destination-host-unreacheble/81560/1 "2020-03-21T10:30:33Z")

</div>

Bonjour!!! S’il vous j’ai bédouin d’aide ma machine ne parviens pas à accéder au serveur DNS , ni pinger

---

<div class="post-metadata">

**Author:** ![anon61356901](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/cab0a1/32.png) [@anon61356901](https://www.debian-fr.org/u/anon61356901)\
**Post date:** [Mars 21, 2020, 11:05 UTC](https://www.debian-fr.org/t/destination-host-unreacheble/81560/2 "2020-03-21T11:05:22Z")

</div>

Bonjour @Koneke

Donne le contenu de ton `/etc/resolv.conf`

```nohighlight
cat /etc/resolv.conf
host 163.172.90.35 # IP de debian-fr.org
ping -c 3 163.172.90.35

```

---

<div class="post-metadata">

**Author:** ![Koneke](https://www.debian-fr.org/user_avatar/www.debian-fr.org/koneke/32/9022_2.png) [@Koneke](https://www.debian-fr.org/u/Koneke)\
**Post date:** [Mars 21, 2020, 1:26 UTC](https://www.debian-fr.org/t/destination-host-unreacheble/81560/3 "2020-03-21T13:26:13Z")

</div>

@anon61356901 Merci d’avance!!  
le `/etc/resolv.conf` :

```nohighlight
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
 nameserver 8.8.8.8
 nameserver 8.8.4.4

```

`host 163.172.90.35` :

```nohighlight
;; connection timed out; no servers could be reached

```

`ping -c 3 163.172.90.35` :

```nohighlight
ping -c 3 163.172.90.35
PING 163.172.90.35 (163.172.90.35) 56(84) bytes of data.
From 192.168.1.113 icmp_seq=1 Destination Host Unreachable
From 192.168.1.113 icmp_seq=2 Destination Host Unreachable
From 192.168.1.113 icmp_seq=3 Destination Host Unreachable

--- 163.172.90.35 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2000ms
pipe 3

```

---

<div class="post-metadata">

**Author:** ![grandtoubab](https://www.debian-fr.org/user_avatar/www.debian-fr.org/grandtoubab/32/4505_2.png) [@grandtoubab](https://www.debian-fr.org/u/grandtoubab)\
**Post date:** [Mars 21, 2020, 3:02 UTC](https://www.debian-fr.org/t/destination-host-unreacheble/81560/4 "2020-03-21T15:02:01Z")

</div>

- Quelle application gère le réseau?
- Le plus simple c’est Network Manager  
[https://wiki.debian.org/fr/NetworkManager](https://wiki.debian.org/fr/NetworkManager)

---

<div class="post-metadata">

**Author:** ![libresurf](https://www.debian-fr.org/user_avatar/www.debian-fr.org/libresurf/32/5259_2.png) [@libresurf](https://www.debian-fr.org/u/libresurf)\
**Post date:** [Mars 21, 2020, 3:16 UTC](https://www.debian-fr.org/t/destination-host-unreacheble/81560/5 "2020-03-21T15:16:13Z")

</div>

> [@Koneke](#):
>
> ```plaintext
> ping -c 3 163.172.90.35
> PING 163.172.90.35 (163.172.90.35) 56(84) bytes of data.
> From 192.168.1.113 icmp_seq=1 Destination Host Unreachable
> From 192.168.1.113 icmp_seq=2 Destination Host Unreachable
> From 192.168.1.113 icmp_seq=3 Destination Host Unreachable
> 
> --- 163.172.90.35 ping statistics ---
> 3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2000ms
> pipe 3
> 
> ```

Ah, pour effectuer cette commande, tu n’as pas besoin de serveur DNS.  
Ton problème n’est donc pas un problème d’accès aux serveurs DNS, mais un problème réseau.

Est-ce que ta carte réseau a été activée par linux ?

Que renvoie la commande `ip addr` ?  
Tu devrais voir apparaître ta carte réseau et les adresses IPv4 (inet) et IPv6 (inet6) qui lui ont été attribuées.

Que renvoie la commande `ip route` ?  
Tu devrais voir apparaître la route par défaut qui pointe vers ta passerelle (généralement ta box internet).

---

<div class="post-metadata">

**Author:** ![Koneke](https://www.debian-fr.org/user_avatar/www.debian-fr.org/koneke/32/9022_2.png) [@Koneke](https://www.debian-fr.org/u/Koneke)\
**Post date:** [Mars 21, 2020, 3:45 UTC](https://www.debian-fr.org/t/destination-host-unreacheble/81560/6 "2020-03-21T15:45:56Z")

</div>

Network manager n’est à peine pas installer…comment reconnètre le manager alors

---

<div class="post-metadata">

**Author:** ![Koneke](https://www.debian-fr.org/user_avatar/www.debian-fr.org/koneke/32/9022_2.png) [@Koneke](https://www.debian-fr.org/u/Koneke)\
**Post date:** [Mars 21, 2020, 5:33 UTC](https://www.debian-fr.org/t/destination-host-unreacheble/81560/7 "2020-03-21T17:33:34Z")

</div>

Voilà ce que j’ai :

```nohighlight
root@asterisk:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    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: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:11:d1:fe brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.113/24 brd 192.168.1.255 scope global enp0s3
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:27ff:fe11:d1fe/64 scope link
       valid_lft forever preferred_lft forever
3: enp0s8: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 08:00:27:6b:68:ba brd ff:ff:ff:ff:ff:ff

```

---

<div class="post-metadata">

**Author:** ![Koneke](https://www.debian-fr.org/user_avatar/www.debian-fr.org/koneke/32/9022_2.png) [@Koneke](https://www.debian-fr.org/u/Koneke)\
**Post date:** [Mars 21, 2020, 5:36 UTC](https://www.debian-fr.org/t/destination-host-unreacheble/81560/8 "2020-03-21T17:36:54Z")

</div>

Je pense bien que ma carte est activée par linux

ip route :

```nohighlight
default via 192.168.1.254 dev enp0s3 onlink
192.168.1.0/24 dev enp0s3 proto kernel scope link src 192.168.1.113

```

---

<div class="post-metadata">

**Author:** ![anon61356901](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/cab0a1/32.png) [@anon61356901](https://www.debian-fr.org/u/anon61356901)\
**Post date:** [Mars 21, 2020, 8:34 UTC](https://www.debian-fr.org/t/destination-host-unreacheble/81560/9 "2020-03-21T20:34:23Z")

</div>

Tu peux essayer de joindre la box / le modem routeur / la passerelle :

```nohighlight
ping -c 3 192.168.1.254

```

Voir si `NetworkManager` est utilisé :

```nohighlight
nmcli

```

Et donner le contenu de `/etc/network/interfaces`

```nohighlight
cat /etc/network/interfaces

```

---

<div class="post-metadata">

**Author:** ![Koneke](https://www.debian-fr.org/user_avatar/www.debian-fr.org/koneke/32/9022_2.png) [@Koneke](https://www.debian-fr.org/u/Koneke)\
**Post date:** [Mars 22, 2020, 12:33 UTC](https://www.debian-fr.org/t/destination-host-unreacheble/81560/10 "2020-03-22T12:33:04Z")

</div>

BONJOUR @anon61356901 !!!

Pour la commande cat /etc/network/interfaces

```nohighlight
> # # This file describes the network interfaces available on your system
   # # and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# # The loopback network interface
auto lo
iface lo inet loopback

auto enp0s3
# # iface enp0s3 inet dhcp
iface enp0s3 inet static
                  address 192.168.1.113
                  netmask 255.255.255.0
                  gateway 192.168.1.254
                  dns-nameservers 8.8.8.8

```

---

<div class="post-metadata">

**Author:** ![Koneke](https://www.debian-fr.org/user_avatar/www.debian-fr.org/koneke/32/9022_2.png) [@Koneke](https://www.debian-fr.org/u/Koneke)\
**Post date:** [Mars 22, 2020, 12:38 UTC](https://www.debian-fr.org/t/destination-host-unreacheble/81560/11 "2020-03-22T12:38:05Z")

</div>

> root@asterisk:~# nmcli  
> The program ‹&nbsp;nmcli&nbsp;› is currently not installed. You can install it by typing:  
> apt install network-manager

> root@asterisk:~# ping -c 3 192.168.1.254  
> PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data.  
> From 192.168.1.113 icmp\_seq=1 Destination Host Unreachable  
> From 192.168.1.113 icmp\_seq=2 Destination Host Unreachable  
> From 192.168.1.113 icmp\_seq=3 Destination Host Unreachable

— 192.168.1.254 ping statistics —  
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2016ms  
pipe 2

Merci d’avance

---

<div class="post-metadata">

**Author:** ![littlejohn75](https://www.debian-fr.org/user_avatar/www.debian-fr.org/littlejohn75/32/3840_2.png) [@littlejohn75](https://www.debian-fr.org/u/littlejohn75)\
**Post date:** [Mars 22, 2020, 1:09 UTC](https://www.debian-fr.org/t/destination-host-unreacheble/81560/12 "2020-03-22T13:09:05Z")

</div>

> [@Koneke](#):
>
> Pour la commande cat /etc/network/interfaces

Je me suis permis de modifier votre message pour y ajouter des balises de texte brut .

La passerelle `192.168.1.254` c’est quoi comme appareil ?  
Si vous avez une box pour vous connecter à internet, il est usuel que cette box qui fait office de passerelle entre le réseau local en 192.168.1.0/24 et internet ait le numéro IP 192.168.1.1  
De plus la plupart du tempsn en plus du routage cette box fait office de  
serveur DHCP  
serveur DNS

```plaintext
fp2@debpacha:~$ nmap 192.168.1.1
Starting Nmap 7.70 ( https://nmap.org ) at 2020-03-22 14:00 CET
Nmap scan report for livebox.home (192.168.1.1)
Host is up (0.015s latency).
Not shown: 996 filtered ports
PORT STATE SERVICE
53/tcp open domain
135/tcp closed msrpc
139/tcp open netbios-ssn
631/tcp open ipp

Nmap done: 1 IP address (1 host up) scanned in 17.63 seconds
fp2@debpacha:~$ 

```

Cordialement,  
Regards,  
Mit freundlichen Grüßen,  
مع تحياتي الخالصة

* * *

F. Petitjean  
Ingénieur civil du Génie Maritime.

« Moi, lorsque je n’ai rien à dire, je veux qu’on le sache. » (R. Devos)

« Celui qui, parti de rien, n’est arrivé nulle part n’a de merci à dire à personne !! »  
Pierre Dac
