# Perte de connexion internet ! **URL:** \ **Category:** Support Debian\ **Created:** [Septembre 6, 2018, 12:14 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468 "2018-09-06T12:14:42Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Papy\_Octet](https://www.debian-fr.org/user_avatar/www.debian-fr.org/papy_octet/32/8503_2.png) [@Papy\_Octet](https://www.debian-fr.org/u/Papy_Octet)\ **Post date:** [Septembre 6, 2018, 12:14 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/1 "2018-09-06T12:14:42Z")
Bonjour, Depuis quelques mois, lorsque je laisse mon ordi de bureau tout seul quelques heures (pour le repas de midi et 
 la sieste 😉 ) il lui arrive d’interrompre la liaison internet. Je n’ai plus de liaison au net par Firefox. Mais aprĂšs avoir fermĂ© Firefox puis le relancĂ©, toujours aucune connexion an Net. Je dois absolument Ă©teindre l’ordi et le redĂ©marrer. Ce problĂšme n’est pas systĂ©matique. Il peut se passer plusieurs jours sans qu’il n’apparaisse. Un tel problĂšme pourrait-il ĂȘtre dĂ» Ă  Debian ? Je n’utilise que les mises Ă  jour officielles pour mes logiciels y compris Debian. Les autres logiciels continuent de fonctionner tant qu’ils ne demandent pas d’accĂšs au Net. Je suis connectĂ© par cĂąble Ă  une B-Box 2 sur un rĂ©seau Proximus (en Belgique). Merci. ---
**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:** [Septembre 6, 2018, 12:53 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/2 "2018-09-06T12:53:15Z")
> [@Papy\_Octet](#): > > Je dois absolument Ă©teindre l’ordi et le redĂ©marrer. Pourquoi absolument ? Il y a des mĂ©thodes un peu moins brutales de relancer les services rĂ©seau. > [@Papy\_Octet](#): > > Je suis connectĂ© par cĂąble Ă  une B-Box 2 sur un rĂ©seau Proximus (en Belgique). En principe une connexion par cĂąble c’est assez fiable, on ne s’amuse pas Ă  dĂ©brancher et rebrancher tous les 36 du mois. > [@Papy\_Octet](#): > > Ce problĂšme n’est pas systĂ©matique. Il peut se passer plusieurs jours sans qu’il n’apparaisse. TrĂšs souvent, on dit qu’on n’a plus de connexion internet alors que c’est simplement la rĂ©solution de noms (DNS) qui a un souci temporaire. Pour en savoir plus sur votre installation, pouvez-vous lancer les commandes suivantes ? ```auto lsb_release -a cat /etc/resolv.conf host google.be ping -c 2 google.be systemctl status -l networking.service ``` Et quand vous perdez la connexion au Net, tentez ```auto sudo systemctl restart networking.service ``` Cordialement, Regards, Mit freundlichen GrĂŒĂŸen, مŰč ŰȘŰ­ÙŠŰ§ŰȘي Ű§Ù„ŰźŰ§Ù„Ű”Ű© * * * F. Petitjean IngĂ©nieur civil du GĂ©nie Maritime. « L’amour, c’est comme les spaghettis, quand c’est mou, c’est cuit. » Proverbe belge ---
**Author:** ![Papy\_Octet](https://www.debian-fr.org/user_avatar/www.debian-fr.org/papy_octet/32/8503_2.png) [@Papy\_Octet](https://www.debian-fr.org/u/Papy_Octet)\ **Post date:** [Septembre 6, 2018, 1:09 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/3 "2018-09-06T13:09:37Z")
Bonjour littlejohn75, Voici les retour de console : ```plaintext ~$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 9.5 (stretch) Release: 9.5 Codename: stretch ``` ```plaintext ~$ cat /etc/resolv.conf # Generated by NetworkManager search home nameserver 192.168.1.1 ``` ```plaintext ~$ host google.be google.be has address 172.217.19.195 google.be has IPv6 address 2a00:1450:400e:802::2003 google.be mail is handled by 20 alt1.aspmx.l.google.com. google.be mail is handled by 50 alt4.aspmx.l.google.com. google.be mail is handled by 30 alt2.aspmx.l.google.com. google.be mail is handled by 40 alt3.aspmx.l.google.com. google.be mail is handled by 10 aspmx.l.google.com. ``` ```plaintext ~$ ping -c 2 google.be PING google.be (172.217.20.99) 56(84) bytes of data. 64 bytes from ams17s01-in-f3.1e100.net (172.217.20.99): icmp_seq=1 ttl=56 time=29.5 ms 64 bytes from ams17s01-in-f3.1e100.net (172.217.20.99): icmp_seq=2 ttl=56 time=29.6 ms --- google.be ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 29.546/29.610/29.675/0.183 ms ``` > ~$ systemctl status -l networking.service > ● networking.service - Raise network interfaces > Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor prese > Active: active (exited) since Thu 2018-09-06 13:55:35 CEST; 1h 0min ago > Docs: man:interfaces(5) > Process: 473 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0 > Process: 468 ExecStartPre=/bin/sh -c [« $CONFIGURE\_INTERFACES Â» != « no Â»] && [ > Main PID: 473 (code=exited, status=0/SUCCESS) > Tasks: 0 (limit: 4915) > CGroup: /system.slice/networking.service > > Warning: Journal has been rotated since unit was started. Log output is incomple > lines 1-11/11 (END)
skipping
 > ● networking.service - Raise network interfaces > Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor prese > Active: active (exited) since Thu 2018-09-06 13:55:35 CEST; 1h 0min ago > Docs: man:interfaces(5) > Process: 473 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0 > Process: 468 ExecStartPre=/bin/sh -c [« $CONFIGURE\_INTERFACES Â» != « no Â»] && [ > Main PID: 473 (code=exited, status=0/SUCCESS) > Tasks: 0 (limit: 4915) > CGroup: /system.slice/networking.service > > Warning: Journal has been rotated since unit was started. Log output is incomple > ~ > ~ > ~ (ceci rĂ©pĂ©tĂ© 30 fois) > lines 1-11/11 (END)
skipping
 > 
 30 rĂ©pĂ©titions de ce qui suit. > ● networking.service - Raise network interfaces > Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) > Active: active (exited) since Thu 2018-09-06 13:55:35 CEST; 1h 0min ago > Docs: man:interfaces(5) > Process: 473 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS) > Process: 468 ExecStartPre=/bin/sh -c [« $CONFIGURE\_INTERFACES Â» != « no Â»] && [ -n "$(ifquery --read-environment > Main PID: 473 (code=exited, status=0/SUCCESS) > Tasks: 0 (limit: 4915) > CGroup: /system.slice/networking.service > > Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > ~ > lines 1-11/11 (END) Merci de t’intĂ©resser Ă  mon petit problĂšme 😉 ---
**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:** [Septembre 6, 2018, 2:27 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/4 "2018-09-06T14:27:08Z")
> [@Papy\_Octet](#): > > Warning: Journal has been rotated since unit was started. Log output is incomple > > ~ > > ~ > > ~ (ceci rĂ©pĂ©tĂ© 30 fois) > > lines 1-11/11 (END)
skipping
 > > 
 30 rĂ©pĂ©titions de ce qui suit. > > ● networking.service - Raise network interfaces 30 rĂ©pĂ©titions, rotation des journaux au bout d’une heure Ă  peine, ce n’est pas normal. DĂ©terminez ce qui provoque une rotation intempestive des journaux. Investiguez avec les commandes suivantes ```auto cd /var/log/ ls -lApst | less sudo dmesg | less ``` Dans le sortie des messages du noyau, faites une recherche sur _'link_ pour confirmer qu’il y a bien 30 tentatives pour mettre en route le rĂ©seau (vous avez un compteur en secondes de la date de l’enregistrement en dĂ©but de ligne). Pour dĂ©terminer le pilote de votre carte rĂ©seau, donnez le retour de ```auto lspci -k | fgrep -i net -A3 ``` 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) ---
**Author:** ![Papy\_Octet](https://www.debian-fr.org/user_avatar/www.debian-fr.org/papy_octet/32/8503_2.png) [@Papy\_Octet](https://www.debian-fr.org/u/Papy_Octet)\ **Post date:** [Septembre 6, 2018, 2:40 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/5 "2018-09-06T14:40:51Z")
```nohighlight ls -lApst | less 4 -rw-r--r-- 1 root root 371 mai 30 16:39 alternatives.log.4.gz 36 -rw------- 1 root root 34304 mai 7 18:23 messages.save 48 -rw-r----- 1 root adm 47737 mai 7 18:23 messages.save.1 4 drwxr-sr-x+ 3 root systemd-journal 4096 mai 7 07:50 journal/ 8 -rw-r--r-- 1 root root 5157 avr 29 17:11 dpkg.log.5.gz 8 -rw-r--r-- 1 root root 4816 avr 21 10:22 fontconfig.log 4 -rw-r--r-- 1 root root 134 avr 15 07:08 alternatives.log.5.gz 12 -rw-r--r-- 1 root root 11598 mar 30 09:13 dpkg.log.6.gz 4 -rw-r--r-- 1 root root 899 mar 28 06:23 alternatives.log.6.gz 20 -rw-r--r-- 1 root root 18041 mar 3 2018 dpkg.log.7.gz 4 -rw-r--r-- 1 root root 981 fĂ©v 18 2018 alternatives.log.7.gz 12 -rw-r--r-- 1 root root 8917 jan 31 2018 dpkg.log.8.gz 4 -rw-r--r-- 1 root root 1153 jan 25 2018 alternatives.log.8.gz 8 -rw-r--r-- 1 root root 5375 dĂ©c 31 2017 dpkg.log.9.gz 4 -rw-r--r-- 1 root root 659 dĂ©c 29 2017 alternatives.log.9.gz 120 -rw-r--r-- 1 root root 122130 dĂ©c 1 2017 dpkg.log.10.gz 8 -rw-r--r-- 1 root root 4778 nov 21 2017 alternatives.log.10.gz 4 drwxr-xr-x 3 root root 4096 nov 21 2017 installer/ 12 -rw-rw-r-- 1 root utmp 292292 nov 21 2017 lastlog 8 -rw-r--r-- 1 root root 32032 nov 21 2017 faillog 4 drwxr-xr-x 3 root root 4096 nov 21 2017 hp/ 4 drwx------ 2 speech-dispatcher root 4096 aoĂ» 8 2017 speech-dispatcher/ 4 drwx--x--x 2 root Debian-gdm 4096 jun 6 2017 gdm3/ ``` La recherche sur “link” ne donne que 4 lignes : ```nohighlight [16.746946] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready [16.959844] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready [18.483479] e1000e: eno1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None [18.483482] e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO [18.483523] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready ``` ```nohighlight ~$ lspci -k | fgrep -i net -A3 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V Subsystem: ASUSTeK Computer Inc. Ethernet Connection (2) I218-V Kernel driver in use: e1000e Kernel modules: e1000e 00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2 ``` ---
**Author:** ![PascalHambourg](https://www.debian-fr.org/user_avatar/www.debian-fr.org/pascalhambourg/32/5837_2.png) [@PascalHambourg](https://www.debian-fr.org/u/PascalHambourg)\ **Post date:** [Septembre 6, 2018, 3:32 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/6 "2018-09-06T15:32:43Z")
> [@Papy\_Octet](#): > > il lui arrive d’interrompre la liaison internet. Je n’ai plus de liaison au net par Firefox. Mais encore ? > [@Papy\_Octet](#): > > Mais aprĂšs avoir fermĂ© Firefox puis le relancĂ©, toujours aucune connexion an Net. Normal. Firefox ne gĂšre pas la connexion rĂ©seau, ce n’est qu’un navigateur web. > [@Papy\_Octet](#): > > Un tel problĂšme pourrait-il ĂȘtre dĂ» Ă  Debian ? Il faut commencer par caractĂ©riser prĂ©cisĂ©ment le problĂšme si on veut avoir une chance d’en trouver la cause. Comparer la sortie des commandes suivantes avant et aprĂšs l’interruption : ``` ip addr ip route ip -6 route cat /etc/resolv.conf ping -nc 4 192.168.1.1 traceroute -n 8.8.8.8 host debian-fr.org ``` ---
**Author:** ![Papy\_Octet](https://www.debian-fr.org/user_avatar/www.debian-fr.org/papy_octet/32/8503_2.png) [@Papy\_Octet](https://www.debian-fr.org/u/Papy_Octet)\ **Post date:** [Septembre 6, 2018, 3:41 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/7 "2018-09-06T15:41:42Z")
Merci Ă  vous pour vos aides prĂ©cieuses. Je regarde tout ça et je reviens dĂšs que j’aurai eu une nouvelle perte du rĂ©seau. A+ ---
**Author:** ![jweber](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/j/e95f7d/32.png) [@jweber](https://www.debian-fr.org/u/jweber)\ **Post date:** [Septembre 6, 2018, 8:34 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/8 "2018-09-06T20:34:48Z")
Un test ras des pĂąquerettes : quand il y a perte de connexion les leds du connecteur rj45 sont-elles encore allumĂ©es ? Je dis çà parceque chez moi sur des pc pas tout jeunes les contacts dans ces connecteurs sont fatiguĂ©s ! et parfois la connexion s’interrompt au niveau physique le plus bas. ---
**Author:** ![Papy\_Octet](https://www.debian-fr.org/user_avatar/www.debian-fr.org/papy_octet/32/8503_2.png) [@Papy\_Octet](https://www.debian-fr.org/u/Papy_Octet)\ **Post date:** [Septembre 7, 2018, 5:34 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/9 "2018-09-07T05:34:51Z")
Bonjour jweber, La connexion rj45 est active. J’ai aussi essayĂ© en dĂ©connectant puis reconnectant le cĂąble, mais comme c’est un ordi de bureau que je ne dĂ©connecte qu’une ou deux fois par ans seulement pour un petit nettoyage il y a peu d’usure de ce cĂŽtĂ©. Une autre possibilitĂ© m’a Ă©tĂ© suggĂ©rĂ©e : un problĂšme dans ma B-Box2, un “dinosaure”, dit-on, et qui peut couper l’internet et le Wifi de temps Ă  autres. Mais je m’interroge alors : est-ce que Debian peut rĂ©tablir la connexion internet lorsque la B-Box2 rĂ©tablit la connexion ? Je ne connaissant pas la commande suggĂ©rĂ©e par littlejohn75 : ```nohighlight sudo systemctl restart networking.service ``` Merci pour ta suggestion 😉 A+ ---
**Author:** ![anon29980398](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/f4b2a3/32.png) [@anon29980398](https://www.debian-fr.org/u/anon29980398)\ **Post date:** [Septembre 7, 2018, 7:18 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/10 "2018-09-07T07:18:34Z")
Bonjour > [@Papy\_Octet](#): > > Je ne connaissant pas la commande suggĂ©rĂ©e par littlejohn75 : Au cas oĂč tu aies envie d’en apprendre un peu plus Ă  ce sujet : > **[systemd pour les administrateurs, partie 1 et 2 - LinuxFr.org](https://linuxfr.org/news/systemd-pour-les-administrateurs-partie-1-et-2)** > > L’actualitĂ© du logiciel libre et des sujets voisins (DIY, Open Hardware, Open Data, les Communs, etc.), sur un site francophone contributif gĂ©rĂ© par une Ă©quipe bĂ©nĂ©vole par et pour des libristes enthousiastes ---
**Author:** ![jweber](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/j/e95f7d/32.png) [@jweber](https://www.debian-fr.org/u/jweber)\ **Post date:** [Septembre 7, 2018, 7:23 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/11 "2018-09-07T07:23:29Z")
> [@Papy\_Octet](#): > > Mais je m’interroge alors : est-ce que Debian peut rĂ©tablir la connexion internet lorsque la B-Box2 rĂ©tablit la connexion ? Oui, sans problĂšme. ---
**Author:** ![PascalHambourg](https://www.debian-fr.org/user_avatar/www.debian-fr.org/pascalhambourg/32/5837_2.png) [@PascalHambourg](https://www.debian-fr.org/u/PascalHambourg)\ **Post date:** [Septembre 7, 2018, 7:49 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/12 "2018-09-07T07:49:18Z")
> [@Papy\_Octet](#): > > Une autre possibilitĂ© m’a Ă©tĂ© suggĂ©rĂ©e : un problĂšme dans ma B-Box2, un “dinosaure”, dit-on, et qui peut couper l’internet et le Wifi de temps Ă  autres. > > Mais je m’interroge alors : est-ce que Debian peut rĂ©tablir la connexion internet lorsque la B-Box2 rĂ©tablit la connexion ? Ça dĂ©pend du mode de panne de la la box (coupure internet ou coupure LAN) et du gestionnaire de connexion (ifupdown, Wicd, NetworkManager
) qui gĂšre l’interface rĂ©seau LAN de ta machine et du mode de configuration (statique, DHCP). D’expĂ©rience ifupdown ne s’en sort pas forcĂ©ment trĂšs bien lorsque l’interface configurĂ©e en DHCP perd sa connexion. ---
**Author:** ![Papy\_Octet](https://www.debian-fr.org/user_avatar/www.debian-fr.org/papy_octet/32/8503_2.png) [@Papy\_Octet](https://www.debian-fr.org/u/Papy_Octet)\ **Post date:** [Septembre 7, 2018, 8:00 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/13 "2018-09-07T08:00:41Z")
@anon29980398 : Merci pour la suggestion. Je vais m’y plonger un peu et essayer de comprendre ce qu’il y est Ă©crit 😉 @jweber : Merci. @PascalHambourg : Je ne pense pas que ce soit une coupure LAN puisque la tĂ©lĂ© connectĂ©e Ă  la B-Box2 continue de fonctionner sans arrĂȘt intempestif ni mĂȘme de ralentissement. La B-Box permet de connecter 2 tĂ©lĂ©s, 2 ordis et elle diffuse le Wifi. Chez moi il n’y a que 1 tĂ©lĂ© et 1 ordi connectĂ© Ă  la box. Au vu des infos collectĂ©e auprĂšs d’utilisateurs et de revendeurs de Proximus : "avec le temps, il se peut que des problĂšmes de coupure arrivent au Wifi et Ă  l’ADSL. Il est peut-ĂȘtre temps de changer de box." Pour ce qui est de la configuration (statique, DHCP, 
) ces termes sont du chinois pour moi 😳 - honte Ă  moi 😜 Mais j’essaie, quand j’ai le temps, de m’instruire. Merci pour vos infos et conseils. A+ ---
**Author:** ![Papy\_Octet](https://www.debian-fr.org/user_avatar/www.debian-fr.org/papy_octet/32/8503_2.png) [@Papy\_Octet](https://www.debian-fr.org/u/Papy_Octet)\ **Post date:** [Septembre 7, 2018, 12:10 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/14 "2018-09-07T12:10:11Z")
Bonjour PascalHambourg, Mon gentil ordi ne m’a pas fait trop attendre cette fois. Il a une nouvelle fois perdu le connexion au net. Voici les retours de la console avant et aprĂšs la coupure 🙂 Avant perte du rĂ©seau. ``` ~$ ip addr 1: lo: 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: eno1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 78:24:af:43:61:d4 brd ff:ff:ff:ff:ff:ff inet 192.168.1.4/24 brd 192.168.1.255 scope global dynamic eno1 valid_lft 10094sec preferred_lft 10094sec inet6 fe80::7a24:afff:fe43:61d4/64 scope link valid_lft forever preferred_lft forever ~$ ip route default via 192.168.1.1 dev eno1 proto static metric 100 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.4 metric 100 ~$ ip -6 route fe80::/64 dev eno1 proto kernel metric 256 pref medium ~$ cat /etc/resolv.conf # Generated by NetworkManager search home nameserver 192.168.1.1 ~$ ping -nc 4 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.957 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.918 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.899 ms 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.898 ms --- 192.168.1.1 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3022ms rtt min/avg/max/mdev = 0.898/0.918/0.957/0.023 ms ~$ traceroute -n 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets 1 192.168.1.1 4.142 ms 4.469 ms 4.790 ms 2 81.241.0.1 88.549 ms 89.213 ms 89.552 ms 3 91.183.242.32 34.687 ms 35.844 ms 39.785 ms 4 91.183.246.108 40.336 ms 42.188 ms 42.465 ms 5 91.183.245.122 48.849 ms 49.128 ms 49.992 ms 6 108.170.241.161 50.550 ms 53.974 ms 108.170.241.129 53.405 ms 7 216.239.63.247 54.202 ms 216.239.41.225 30.455 ms 108.170.236.213 31.927 ms 8 8.8.8.8 32.807 ms 32.896 ms 32.208 ms ~$ host debian-fr.org debian-fr.org has address 163.172.90.35 debian-fr.org has IPv6 address 2001:bc8:280a:1:ff:1:0:100 debian-fr.org mail is handled by 5 mail.zehome.com. AprĂšs perte du rĂ©seau : ~$ ip addr 1: lo: 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: eno1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 78:24:af:43:61:d4 brd ff:ff:ff:ff:ff:ff inet6 fe80::7a24:afff:fe43:61d4/64 scope link valid_lft forever preferred_lft forever ~$ ip route ne retourne rien ! ~$ ip -6 route fe80::/64 dev eno1 proto kernel metric 256 pref medium ~$ cat /etc/resolv.conf # Generated by NetworkManager search home nameserver 192.168.1.1 ~$ ping -nc 4 192.168.1.1 connect: Le rĂ©seau n'est pas accessible ~$ traceroute -n 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets connect: Le rĂ©seau n'est pas accessible ~$ host debian-fr.org ;; connection timed out; no servers could be reached ``` ---
**Author:** ![PascalHambourg](https://www.debian-fr.org/user_avatar/www.debian-fr.org/pascalhambourg/32/5837_2.png) [@PascalHambourg](https://www.debian-fr.org/u/PascalHambourg)\ **Post date:** [Septembre 7, 2018, 12:32 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/15 "2018-09-07T12:32:00Z")
Visiblement l’interface rĂ©seau eno1 a perdu toute sa configuration IP (adresse et routes) bien que l’interface reste activĂ©e et a liaison ethernet reste marquĂ©e comme prĂ©sente. On voit dans le contenu de resolv.conf que ce fichier est gĂ©nĂ©rĂ© par NetworkManager, donc c’est probablement lui qui gĂšre l’interface. Je suppose qu’elle est configurĂ© en automatique (DHCP), Ă  vĂ©rifier dans les paramĂštres de connexion de l’applet NetworkManager du bureau. VĂ©rifie quand mĂȘme qu’il n’y a pas de mention de eno1 dans /etc/network/interfaces ni un fichier inclus par une directive source. Il se peut que le client DHCP (dhclient par dĂ©faut) n’a pas rĂ©ussi Ă  renouveler le bail DHCP pour une raison Ă  dĂ©terminer et a supprimĂ© la configuration IP de l’interface. Il faudrait examiner les logs de dhclient et NetworkManager datant d’un peu avant la coupure dans /var/log/syslog, messages ou daemon.log. ---
**Author:** ![Papy\_Octet](https://www.debian-fr.org/user_avatar/www.debian-fr.org/papy_octet/32/8503_2.png) [@Papy\_Octet](https://www.debian-fr.org/u/Papy_Octet)\ **Post date:** [Septembre 7, 2018, 3:40 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/16 "2018-09-07T15:40:36Z")
Bonsoir, Je viens de regarder dans le contenu du fichier syslog. Je n’y comprends rien mais j’ai trouvĂ© ces quelques lignes se rapportant Ă  Firefox : > ``` > Sep 7 13:03:11 MGD1117 systemd[1]: Started Run anacron jobs. > Sep 7 13:03:11 MGD1117 systemd[1]: anacron.timer: Adding 19.989676s random time. > Sep 7 13:03:11 MGD1117 anacron[5390]: Anacron 2.3 started on 2018-09-07 > Sep 7 13:03:11 MGD1117 anacron[5390]: Normal exit (0 jobs run) > Sep 7 13:13:15 MGD1117 firefox-esr.desktop[2176]: 1536318795948#011Sync.BrowserIDManager#011ERROR#011Non-authentication error in _fetchTokenForUser: TokenServerClientNetworkError({"error":{}}) (resource://gre/modules/services-common/tokenserverclient.js:38:36) JS Stack trace: TokenServerClientNetworkError@tokenserverclient.js:62:16 < onResponse@tokenserverclient.js:273:12 < onStopRequest@rest.js:485:7 < waitForSyncCallback@async.js:98:7 < makeSpinningCallback/callback.wait@async.js:152:27 < this.BrowserIDManager.prototype._getAuthenticationHeader@browserid_identity.js:727:7 < Res __createRequest@resource.js:156:20 < _doRequest@resource.js:181:19 < Res__ request@resource.js:385:7 < Res_get@resource.js:415:12 < Sync11Service.prototype._fetchInfo@service.js:552:14 < sync@enginesync.js:80:16 < onNotify@service.js:1328:7 < WrappedNotify@util.js:166:21 < WrappedLock@util.js:121:16 < _lockedSync@service.js:1318:12 < sync/<@service.js:1310:14 < WrappedCatch@util.js:95:16 < sync@service.js:1298:5 > Sep 7 13:13:16 MGD1117 firefox-esr.desktop[2176]: 1536318795956#011Sync.BrowserIDManager#011ERROR#011Failed to fetch a token for authentication: TokenServerClientNetworkError({"error":{}}) (resource://gre/modules/services-common/tokenserverclient.js:38:36) JS Stack trace: TokenServerClientNetworkError@tokenserverclient.js:62:16 < onResponse@tokenserverclient.js:273:12 < onStopRequest@rest.js:485:7 < waitForSyncCallback@async.js:98:7 < makeSpinningCallback/callback.wait@async.js:152:27 < this.BrowserIDManager.prototype._getAuthenticationHeader@browserid_identity.js:727:7 < Res __createRequest@resource.js:156:20 < _doRequest@resource.js:181:19 < Res__ request@resource.js:385:7 < Res_get@resource.js:415:12 < Sync11Service.prototype._fetchInfo@service.js:552:14 < sync@enginesync.js:80:16 < onNotify@service.js:1328:7 < WrappedNotify@util.js:166:21 < WrappedLock@util.js:121:16 < _lockedSync@service.js:1318:12 < sync/<@service.js:1310:14 < WrappedCatch@util.js:95:16 < sync@service.js:1298:5 > Sep 7 13:13:16 MGD1117 firefox-esr.desktop[2176]: 1536318795966#011Sync.ErrorHandler#011ERROR#011Sync encountered an error: Error: NS_ERROR_UNKNOWN_HOST (resource://services-sync/resource.js:395:19) JS Stack trace: waitForSyncCallback@async.js:98:7 < Res__request@resource.js:386:14 < Res_get@resource.js:415:12 < Sync11Service.prototype._fetchInfo@service.js:552:14 < sync@enginesync.js:80:16 < onNotify@service.js:1328:7 < WrappedNotify@util.js:166:21 < WrappedLock@util.js:121:16 < _lockedSync@service.js:1318:12 < sync/<@service.js:1310:14 < WrappedCatch@util.js:95:16 < sync@service.js:1298:5 < Res_get@resource.js:415:12 < Sync11Service.prototype._fetchInfo@service.js:552:14 < sync@enginesync.js:80:16 < onNotify@service.js:1328:7 < WrappedNotify@util.js:166:21 < WrappedLock@util.js:121:16 < _lockedSync@service.js:1318:12 < sync/<@service.js:1310:14 < WrappedCatch@util.js:95:16 < sync@service.js:1298:5 > Sep 7 13:17:01 MGD1117 CRON[5399]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) > Sep 7 13:53:24 MGD1117 gnome-shell[1779]: clutter_input_device_get_mapping_mode: assertion 'clutter_input_device_get_device_type (device) == CLUTTER_TABLET_DEVICE' failed > Sep 7 13:53:25 MGD1117 gnome-shell[1779]: clutter_input_device_get_mapping_mode: assertion 'clutter_input_device_get_device_type (device) == CLUTTER_TABLET_DEVICE' failed > Sep 7 13:53:25 MGD1117 gnome-shell[1779]: clutter_input_device_get_mapping_mode: assertion 'clutter_input_device_get_device_type (device) == CLUTTER_TABLET_DEVICE' failed > Sep 7 13:53:26 MGD1117 firefox-esr.desktop[2176]: 1536321206718#011FirefoxAccounts#011ERROR#011error POSTing /certificate/sign: {"error":{},"errorString":"[Exception... \"NS_ERROR_UNKNOWN_HOST\" nsresult: \"0x804b001e (NS_ERROR_UNKNOWN_HOST)\" location: \"JS frame :: resource://services-common/rest.js :: onStopRequest :: line 483\" data: no]","message":null,"code":null,"errno":null} > Sep 7 13:53:26 MGD1117 firefox-esr.desktop[2176]: 1536321206718#011FirefoxAccounts#011ERROR#011error POSTing /certificate/sign: {"error":{},"errorString":"[Exception... \"NS_ERROR_UNKNOWN_HOST\" nsresult: \"0x804b001e (NS_ERROR_UNKNOWN_HOST)\" location: \"JS frame :: resource://services-common/rest.js :: onStopRequest :: line 483\" data: no]","message":null,"code":null,"errno":null} > Sep 7 13:53:26 MGD1117 firefox-esr.desktop[2176]: 1536321206718#011FirefoxAccounts#011ERROR#011HAWK.signCertificate error: {"error":{},"errorString":"[Exception... \"NS_ERROR_UNKNOWN_HOST\" nsresult: \"0x804b001e (NS_ERROR_UNKNOWN_HOST)\" location: \"JS frame :: resource://services-common/rest.js :: onStopRequest :: line 483\" data: no]","message":null,"code":null,"errno":null} > Sep 7 13:53:26 MGD1117 firefox-esr.desktop[2176]: 1536321206718#011FirefoxAccounts#011ERROR#011HAWK.signCertificate error: {"error":{},"errorString":"[Exception... \"NS_ERROR_UNKNOWN_HOST\" nsresult: \"0x804b001e (NS_ERROR_UNKNOWN_HOST)\" location: \"JS frame :: resource://services-common/rest.js :: onStopRequest :: line 483\" data: no]","message":null,"code":null,"errno":null} > Sep 7 13:53:26 MGD1117 firefox-esr.desktop[2176]: 1536321206720#011Sync.BrowserIDManager#011ERROR#011Non-authentication error in _fetchTokenForUser: {"error":{},"errorString":"[Exception... \"NS_ERROR_UNKNOWN_HOST\" nsresult: \"0x804b001e (NS_ERROR_UNKNOWN_HOST)\" location: \"JS frame :: resource://services-common/rest.js :: onStopRequest :: line 483\" data: no]","message":null,"code":null,"errno":null} > Sep 7 13:53:26 MGD1117 firefox-esr.desktop[2176]: 1536321206722#011Sync.BrowserIDManager#011ERROR#011Failed to fetch a token for authentication: {"error":{},"errorString":"[Exception... \"NS_ERROR_UNKNOWN_HOST\" nsresult: \"0x804b001e (NS_ERROR_UNKNOWN_HOST)\" location: \"JS frame :: resource://services-common/rest.js :: onStopRequest :: line 483\" data: no]","message":null,"code":null,"errno":null} > Sep 7 13:53:26 MGD1117 firefox-esr.desktop[2176]: 1536321206726#011Sync.ErrorHandler#011ERROR#011Sync encountered an error: Error: NS_ERROR_UNKNOWN_HOST (resource://services-sync/resource.js:395:19) JS Stack trace: waitForSyncCallback@async.js:98:7 < Res__request@resource.js:386:14 < Res_get@resource.js:415:12 < Sync11Service.prototype._fetchInfo@service.js:552:14 < sync@enginesync.js:80:16 < onNotify@service.js:1328:7 < WrappedNotify@util.js:166:21 < WrappedLock@util.js:121:16 < _lockedSync@service.js:1318:12 < sync/<@service.js:1310:14 < WrappedCatch@util.js:95:16 < sync@service.js:1298:5 < Res_get@resource.js:415:12 < Sync11Service.prototype._fetchInfo@service.js:552:14 < sync@enginesync.js:80:16 < onNotify@service.js:1328:7 < WrappedNotify@util.js:166:21 < WrappedLock@util.js:121:16 < _lockedSync@service.js:1318:12 < sync/<@service.js:1310:14 < WrappedCatch@util.js:95:16 < sync@service.js:1298:5 > Sep 7 13:53:27 MGD1117 gnome-software-service.desktop[1939]: 11:53:27:0948 Gs no app for changed apps-menu@gnome-shell-extensions.gcampax.github.com > Sep 7 13:53:28 MGD1117 gnome-software-service.desktop[1939]: 11:53:28:0328 Gs no app for changed apt-update-indicator@franglais125.gmail.com > Sep 7 13:54:00 MGD1117 PackageKit: get-updates transaction /2533_ecaeaadd from uid 1000 finished with success after 395ms > Sep 7 13:54:14 MGD1117 dbus-daemon[1693]: Activating service name='org.gnome.gedit' > Sep 7 13:54:15 MGD1117 dbus-daemon[1693]: Successfully activated service 'org.gnome.gedit' > Sep 7 13:54:19 MGD1117 gedit[5496]: Allocating size to GtkOverlay 0x564490ff1130 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? > Sep 7 13:54:51 MGD1117 dbus-daemon[1693]: Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' > Sep 7 13:54:51 MGD1117 systemd[1675]: Starting GNOME Terminal Server... > Sep 7 13:54:51 MGD1117 dbus-daemon[1693]: Successfully activated service 'org.gnome.Terminal' > Sep 7 13:54:51 MGD1117 systemd[1675]: Started GNOME Terminal Server. > Sep 7 14:01:04 MGD1117 tracker-extract[1907]: unable to create file '/run/user/1000/dconf/user': Permission non accordĂ©e. dconf will not work properly. > Sep 7 14:01:04 MGD1117 systemd[1]: Started Run anacron jobs. > Sep 7 14:01:04 MGD1117 anacron[5566]: Anacron 2.3 started on 2018-09-07 > Sep 7 14:01:04 MGD1117 systemd[1]: anacron.timer: Adding 2min 1.130952s random time. > Sep 7 14:01:04 MGD1117 anacron[5566]: Normal exit (0 jobs run) > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x2C0048,name=PBrowser::Msg ___delete__ ) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x2C0048,name=PBrowser::Msg ___delete__ ) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x2C0048,name=PBrowser::Msg ___delete__ ) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x2C0048,name=PBrowser::Msg ___delete__ ) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x2C0048,name=PBrowser::Msg ___delete__ ) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x2C0048,name=PBrowser::Msg ___delete__ ) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x2C0048,name=PBrowser::Msg ___delete__ ) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x2C0048,name=PBrowser::Msg ___delete__ ) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x2C0048,name=PBrowser::Msg ___delete__ ) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x4600AC,name=PContent::Msg_ScriptError) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x460102,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x2C0048,name=PBrowser::Msg ___delete__ ) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:09 MGD1117 firefox-esr.desktop[2176]: ###!!! [Child][MessageChannel] Error: (msgtype=0x4600AB,name=PContent::Msg_ConsoleMessage) Channel closing: too late to send/recv, messages will be lost > Sep 7 14:02:14 MGD1117 tracker-extract[1907]: unable to create file '/run/user/1000/dconf/user': Permission non accordĂ©e. dconf will not work properly. > Sep 7 14:02:20 MGD1117 gnome-session[1695]: gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:20 MGD1117 gnome-session[1695]: gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:20 MGD1117 gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:20 MGD1117 gnome-session[1695]: gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:20 MGD1117 gnome-session[1695]: gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:20 MGD1117 gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:20 MGD1117 gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:20 MGD1117 gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:20 MGD1117 gnome-session[1695]: gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:20 MGD1117 gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:22 MGD1117 gnome-session[1695]: gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:22 MGD1117 gnome-session[1695]: gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:22 MGD1117 gnome-session[1695]: gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:22 MGD1117 gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:22 MGD1117 gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:22 MGD1117 gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:22 MGD1117 gnome-session[1695]: gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:22 MGD1117 gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:22 MGD1117 gnome-session[1695]: gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:22 MGD1117 gnome-session-binary[1695]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Sep 7 14:02:23 MGD1117 systemd[1]: Stopping Daemon for power management... > Sep 7 14:02:25 MGD1117 kernel: [24322.819230] usb 3-2: USB disconnect, device number 6 > Sep 7 14:03:17 MGD1117 systemd-modules-load[246]: Inserted module 'lp' > Sep 7 14:03:17 MGD1117 systemd[1]: Mounted Debug File System. > Sep 7 14:03:17 MGD1117 kernel: [0.000000] Linux version 4.9.0-8-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21) > Sep 7 14:03:17 MGD1117 systemd[1]: Mounted POSIX Message Queue File System. > Sep 7 14:03:17 MGD1117 systemd[1]: Mounted Huge Pages File System. > Sep 7 14:03:17 MGD1117 systemd[1]: Started Remount Root and Kernel File Systems. > > ``` J’espĂšre que ça pourra ĂȘtre utile. Merci. ---
**Author:** ![PascalHambourg](https://www.debian-fr.org/user_avatar/www.debian-fr.org/pascalhambourg/32/5837_2.png) [@PascalHambourg](https://www.debian-fr.org/u/PascalHambourg)\ **Post date:** [Septembre 7, 2018, 3:52 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/17 "2018-09-07T15:52:42Z")
Non, rien Ă  voir avec firefox. C’est un problĂšme de configuration de l’interface rĂ©seau, a minima, et je rĂ©pĂšte que firefox n’est qu’un navigateur. ---
**Author:** ![Papy\_Octet](https://www.debian-fr.org/user_avatar/www.debian-fr.org/papy_octet/32/8503_2.png) [@Papy\_Octet](https://www.debian-fr.org/u/Papy_Octet)\ **Post date:** [Septembre 7, 2018, 4:02 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/18 "2018-09-07T16:02:55Z")
VoilĂ  le fichier syslog en question. [syslog 07-09.txt](https://www.debian-fr.org/uploads/default/original/2X/4/4e1e1fc65a0ac922b015e67e92549b760456af0a.txt) (408,1 Ko) ---
**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:** [Septembre 7, 2018, 10:37 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/19 "2018-09-07T22:37:25Z")
> [@Papy\_Octet](#): > > VoilĂ  le fichier syslog en question. Ce journal contient une foule d’informations et il est difficile de filtrer tout cela pour se concentrer sur vos problĂšmes de connexion. Dans votre message #14 vous n’avez pas indiquĂ© Ă  quelle heure vous avez subi la coupure, mais ce serait vers 14h d’aprĂšs le message #16. ```auto Sep 7 14:02:23 MGD1117 systemd[1]: Stopping Daemon for power management... Sep 7 14:02:25 MGD1117 kernel: [24322.819230] usb 3-2: USB disconnect, device number 6 Sep 7 14:03:17 MGD1117 systemd-modules-load[246]: Inserted module 'lp' Sep 7 14:03:17 MGD1117 systemd[1]: Mounted Debug File System. Sep 7 14:03:17 MGD1117 kernel: [0.000000] Linux version 4.9.0-8-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21) Sep 7 14:03:17 MGD1117 systemd[1]: Mounted POSIX Message Queue File System. Sep 7 14:03:17 MGD1117 systemd[1]: Mounted Huge Pages File System. ``` Ceci nous montre que le systĂšme a redĂ©marrĂ© Ă  14h 03 minutes et 17 secondes, que la machine s’appelle `MGD1117` et la version du noyau. Vous avez un bureau gnome et le gestionnaire de connexion en mode graphique est `gdm3` comme le montre les 1043 lignes Ă©mises par `/usr/lib/gdm3/gdm-x-session` (faudrait dire aux dĂ©veloppeurs de se calmer avec les journaux, moi avec xfce je n’ai que 12 lignes Ă©mises par `lightdm`). Il y a un certain nombre d’informations relativement confidentielles qui transparaissent dans les messages Ă©mis par `tracker-extract`, en particulier les chemins de fichiers PDF qui seraient corrompus. Si vous faites partie du groupe `adm` lancez ```auto fgrep tracker-extract /var/log/syslog | less ``` et en recherchant sur le nom du pilote de la carte rĂ©seau ```auto Sep 7 14:03:17 MGD1117 kernel: [1.007889] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection Sep 7 14:03:17 MGD1117 kernel: [1.007916] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF Sep 7 14:03:17 MGD1117 kernel: [1.008416] e1000e 0000:00:19.0 eno1: renamed from eth0 Sep 7 14:03:22 MGD1117 kernel: [19.144203] e1000e: eno1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None Sep 7 14:03:22 MGD1117 kernel: [19.144206] e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO ``` Il semblerait que la box n’accepte qu’une connexion Ă  100 Mbps, et sans contrĂŽle de flux. Il y a tellement d’erreurs dans le journal que cela devient difficile de s’y retrouver. Par exemple, firefox a des problĂšmes avec la mise Ă  jour des addons Ă  8 h du mat. C’est beaucoup trop tĂŽt 😀 Si vous soupçonnez un problĂšme de connexion, fermez firefox (le navigateur fait plusieurs tentatives qui Ă©chouent ce qui remplit les journaux) et lancez ```auto systemctl status network-manager.service ``` ordialement, Regards, Mit freundlichen GrĂŒĂŸen, مŰč ŰȘŰ­ÙŠŰ§ŰȘي Ű§Ù„ŰźŰ§Ù„Ű”Ű© * * * F. Petitjean IngĂ©nieur civil du GĂ©nie Maritime. Linux: the operating system with a CLUE
 Command Line User Environment. – seen in a posting in comp.software.testing ---
**Author:** ![PascalHambourg](https://www.debian-fr.org/user_avatar/www.debian-fr.org/pascalhambourg/32/5837_2.png) [@PascalHambourg](https://www.debian-fr.org/u/PascalHambourg)\ **Post date:** [Septembre 7, 2018, 10:58 UTC](https://www.debian-fr.org/t/perte-de-connexion-internet/77468/20 "2018-09-07T22:58:46Z")
Le problĂšme semble s’ĂȘtre dĂ©clenchĂ© bien plus tĂŽt, vers 11h18. @Papy_Octet : dans le message n° 14 la sortie d’ip addr avant la coupure indique que l’adresse IP de l’interface en1 est 192.168.1.4 mais le fichier syslog contient de façon constante l’adresse 192.168.1.5. Il semble donc y avoir une incohĂ©rence. De quand exactement date cette sortie d’ip addr ? Les messages intĂ©ressants sont ceux de dhclient et de NetworkManager. On voit plusieurs renouvellements rĂ©ussis du bail DHCP, comme ``` Sep 7 09:49:03 MGD1117 dhclient[621]: DHCPREQUEST of 192.168.1.5 on eno1 to 192.168.1.1 port 67 Sep 7 09:49:03 MGD1117 dhclient[621]: DHCPACK of 192.168.1.5 from 192.168.1.1 Sep 7 09:49:03 MGD1117 NetworkManager[539]: [1536306543.7726] dhcp4 (eno1): address 192.168.1.5 Sep 7 09:49:03 MGD1117 NetworkManager[539]: [1536306543.7727] dhcp4 (eno1): plen 24 (255.255.255.0) Sep 7 09:49:03 MGD1117 NetworkManager[539]: [1536306543.7727] dhcp4 (eno1): gateway 192.168.1.1 Sep 7 09:49:03 MGD1117 NetworkManager[539]: [1536306543.7727] dhcp4 (eno1): server identifier 192.168.1.1 Sep 7 09:49:03 MGD1117 NetworkManager[539]: [1536306543.7727] dhcp4 (eno1): lease time 10800 ``` Puis soudain le serveur DHCP refuse de renouveler le bail, qui expire de fait : ``` Sep 7 11:18:44 MGD1117 dhclient[621]: DHCPREQUEST of 192.168.1.5 on eno1 to 192.168.1.1 port 67 Sep 7 11:18:45 MGD1117 dhclient[621]: DHCPNAK from 192.168.1.1 Sep 7 11:18:45 MGD1117 NetworkManager[539]: [1536311925.3872] dhcp4 (eno1): state changed bound -> expire Sep 7 11:18:45 MGD1117 NetworkManager[539]: [1536311925.5586] dhcp4 (eno1): canceled DHCP transaction, DHCP client pid 621 Sep 7 11:18:45 MGD1117 NetworkManager[539]: [1536311925.5587] dhcp4 (eno1): state changed expire -> done Sep 7 11:18:45 MGD1117 NetworkManager[539]: [1536311925.6338] device (eno1): scheduling DHCPv4 restart in 120 seconds, 3 tries left (reason: lease expired) ``` Ensuite NetworkManager fait deux autres tentatives de relancer dhclient qui redemande la mĂȘme adresse, mais sans plus de succĂšs. Je suppose que c’est Ă  ce moment que l’interface eno1 a Ă©tĂ© dĂ©configurĂ©e. Et plus rien ne se passe jusqu’au redĂ©marrage Ă  14h03. Pour le moment je n’ai pas la moindre idĂ©e de ce qui a pu causer le refus de la box de renouveler le bail DHCP. Il faudrait commencer par tirer au clair l’incohĂ©rence entre les adresses IP affichĂ©e par ip addr et dans le fichier syslog. [Page suivante](https://www.debian-fr.org/t/perte-de-connexion-internet/77468.md?page=2)