Re: Probleme reseau

Pàgina inicial

Reply to this message
Autor: Dominique Fournier
Data:  
A: guilde
Assumpte: Re: Probleme reseau
Bonjour

Le message "reason 'user-requested'" indiquerait peut-être un service
qui demande de mettre en veille l'interface. Economie d'énergie ?

Bonne journée

Dom

Le 26/02/2019 à 20:31, Patrick Dupre a écrit :
> Bonjour,
>
> Oui, les connections ont ete testes,
> C'est une connection par carte mere integree d'un PC Dell flambant neuf.
>
> J'ai aussi change la vitesse: 10 et 100 Mbit/s, mais pas de difference.
> J'ai aussi essaye de reproduire le probleme.
> La seule chose certaine pour l'instant est la non disponibilite
> du reseau (bien que connecte) lorsque je demmare le PC apres
> une nuit.
> Le temps de reconnection est de 5 a 20 mn.
>
> Voici un journalctl.
> Ce qui me parait bizarre c'est cela:
> +++++++++++++++++++++++++++++++++++++++++++++
>
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9960] manager: NetworkManager state is now CONNECTED_LOCAL
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9990] manager: NetworkManager state is now CONNECTED_SITE
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9991] policy: set 'eno1' (eno1) as default for IPv4 routing and DNS
> Feb 25 18:26:27 homere NetworkManager[1273]: <info> [1551115587.0027] device (eno1): Activation: successful, device activated.
> Feb 25 18:26:27 homere NetworkManager[1273]: <info> [1551115587.0032] manager: startup complete
> Feb 25 18:26:27 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Feb 25 18:26:36 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Feb 25 18:26:56 homere NetworkManager[1273]: <info> [1551115616.9518] connectivity: (eno1) timed out
> ++++++++++++++++++++++++++++++++++++++++
> CONNECTED_LOCAL
> CONNECTED_SITE
> puis, on est passe en timeout semble-t'il a cause d'un SERVICE_STOP !!!!
> Pourquoi ?
>
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Feb 25 18:26:56 homere dbus-daemon[1104]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=1273 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
> Feb 25 18:26:56 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Feb 25 18:27:06 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Feb 25 18:31:52 homere NetworkManager[1273]: <info> [1551115912.9518] connectivity: (eno1) timed out
> ++++++++++++++++++++++++++++
> de nouveau en timeout a cause d'un SERVICE_STOP
> puis 5 mn plus tard, soudainement !!!!
> +++++++++++++++++++++++++++++++++++++++++
> Feb 25 18:36:23 homere NetworkManager[1273]: <info> [1551116183.3831] manager: NetworkManager state is now CONNECTED_GLOBAL
> Feb 25 18:36:23 homere dbus-daemon[1104]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=1273 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
> Feb 25 18:36:23 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> +++++++++++++++++++++++++++++++++++++++++++++
> enfin
> CONNECTED_GLOBAL
> qui semble etre le fontinnement correct.
>
> Pourquoi ce lapse de temps 10 mn ?
> Normalement on devrait avoir:
>
>
> Feb 26 19:03:34 Teucidide NetworkManager[1362]: <info> [1551204214.4744] manager: NetworkManager state is now CONNECTED_LOCAL
> Feb 26 19:03:34 Teucidide NetworkManager[1362]: <info> [1551204214.4768] manager: NetworkManager state is now CONNECTED_SITE
> Feb 26 19:03:34 Teucidide NetworkManager[1362]: <info> [1551204214.4769] policy: set 'enp2s0' (enp2s0) as default for IPv4 routing and DNS
> Feb 26 19:03:34 Teucidide NetworkManager[1362]: <info> [1551204214.4797] device (enp2s0): Activation: successful, device activated.
> Feb 26 19:03:34 Teucidide NetworkManager[1362]: <info> [1551204214.4801] manager: startup complete
> Feb 26 19:03:34 Teucidide audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Feb 26 19:03:34 Teucidide NetworkManager[1362]: <info> [1551204214.7522] manager: NetworkManager state is now CONNECTED_GLOBAL
>
>
> Je ferai un autre journalctl demain.
>
> je ferai aussi un
> systemctl stop/start NetworkManager.service
> pour voir si cela permet la connextion.
>
> Merci.
>
> +++++++++++++++++++++++++++++++++++++++++++
> Feb 25 18:25:32 homere NetworkManager[1287]: <info> [1551115532.5356] modem-manager: ModemManager no longer available
> Feb 25 18:25:32 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Feb 25 18:25:32 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Feb 25 18:25:32 homere NetworkManager[1287]: <info> [1551115532.8544] caught SIGTERM, shutting down normally.
> Feb 25 18:25:32 homere NetworkManager[1287]: <info> [1551115532.8586] exiting (success)
> Feb 25 18:25:32 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Feb 25 18:25:32 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.7456] NetworkManager (version 1.10.12-3.fc28) is starting... (for the first time)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.7458] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity-fedora.conf)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.7510] manager[0x55f65db5f0e0]: monitoring kernel firmware directory '/lib/firmware'.
> Feb 25 18:26:22 homere dbus-daemon[1104]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.10' (uid=0 pid=1273 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8262] hostname: hostname: using hostnamed
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8262] hostname: hostname changed from (none) to "homere"
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8264] dns-mgr[0x55f65db79930]: init: dns=default, rc-manager=symlink
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8268] manager[0x55f65db5f0e0]: rfkill: WiFi hardware radio set enabled
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8269] manager[0x55f65db5f0e0]: rfkill: WWAN hardware radio set enabled
> Feb 25 18:26:22 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Feb 25 18:26:22 homere dbus-daemon[1104]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=1273 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
> Feb 25 18:26:22 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8485] settings: loaded plugin ifcfg-rh: (c) 2007 - 2015 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. (/usr/lib64/NetworkManager/libnm-settings-plugin-ifcfg-rh.so)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8510] settings: loaded plugin iBFT: (c) 2014 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. (/usr/lib64/NetworkManager/libnm-settings-plugin-ibft.so)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8511] settings: loaded plugin keyfile: (c) 2007 - 2016 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8518] ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-eno1 (e418d605-b034-3bdb-a1c5-c18642d7e304,"eno1")
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8665] manager: rfkill: WiFi enabled by radio killswitch; enabled by state file
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8666] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8666] manager: Networking is enabled by state file
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8668] dhcp-init: Using DHCP client 'dhclient'
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMBondDeviceFactory (internal)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMBridgeDeviceFactory (internal)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMDummyDeviceFactory (internal)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMEthernetDeviceFactory (internal)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMInfinibandDeviceFactory (internal)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMIPTunnelDeviceFactory (internal)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMMacsecDeviceFactory (internal)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMMacvlanDeviceFactory (internal)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMPppDeviceFactory (internal)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8682] Loaded device plugin: NMTunDeviceFactory (internal)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8682] Loaded device plugin: NMVethDeviceFactory (internal)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8682] Loaded device plugin: NMVlanDeviceFactory (internal)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8682] Loaded device plugin: NMVxlanDeviceFactory (internal)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8720] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/libnm-device-plugin-adsl.so)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8780] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8796] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wifi.so)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8826] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/libnm-device-plugin-team.so)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8837] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wwan.so)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8850] device (lo): carrier: link connected
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8855] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8863] manager: (eno1): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
> Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8868] device (eno1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
> Feb 25 18:26:23 homere NetworkManager[1273]: <info> [1551115583.1068] modem-manager: ModemManager available
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9163] device (eno1): carrier: link connected
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9181] device (eno1): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9201] policy: auto-activating connection 'eno1'
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9230] device (eno1): Activation: starting connection 'eno1' (e418d605-b034-3bdb-a1c5-c18642d7e304)
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9236] device (eno1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9240] manager: NetworkManager state is now CONNECTING
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9252] device (eno1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9350] device (eno1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9358] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9408] dhcp4 (eno1): dhclient started with pid 1845
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9851] dhcp4 (eno1): address 192.168.13.3
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9851] dhcp4 (eno1): plen 22 (255.255.252.0)
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9852] dhcp4 (eno1): gateway 192.168.12.1
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9852] dhcp4 (eno1): lease time 86400
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9852] dhcp4 (eno1): nameserver '192.168.4.7'
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9852] dhcp4 (eno1): nameserver '192.168.4.2'
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9852] dhcp4 (eno1): domain name 'icb-cnrs.net'
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9852] dhcp4 (eno1): state changed unknown -> bound
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9860] device (eno1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9957] device (eno1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9959] device (eno1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9960] manager: NetworkManager state is now CONNECTED_LOCAL
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9990] manager: NetworkManager state is now CONNECTED_SITE
> Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9991] policy: set 'eno1' (eno1) as default for IPv4 routing and DNS
> Feb 25 18:26:27 homere NetworkManager[1273]: <info> [1551115587.0027] device (eno1): Activation: successful, device activated.
> Feb 25 18:26:27 homere NetworkManager[1273]: <info> [1551115587.0032] manager: startup complete
> Feb 25 18:26:27 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Feb 25 18:26:36 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Feb 25 18:26:56 homere NetworkManager[1273]: <info> [1551115616.9518] connectivity: (eno1) timed out
> Feb 25 18:26:56 homere dbus-daemon[1104]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=1273 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
> Feb 25 18:26:56 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Feb 25 18:27:06 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Feb 25 18:31:52 homere NetworkManager[1273]: <info> [1551115912.9518] connectivity: (eno1) timed out
> Feb 25 18:36:23 homere NetworkManager[1273]: <info> [1551116183.3831] manager: NetworkManager state is now CONNECTED_GLOBAL
> Feb 25 18:36:23 homere dbus-daemon[1104]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=1273 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
> Feb 25 18:36:23 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Feb 25 18:36:33 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
>
> ===========================================================================
>   Patrick DUPRÉ                                 | | email: pdupre@???
>   Laboratoire interdisciplinaire Carnot de Bourgogne
>   9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
>   Tel: +33 (0)380395988
> ===========================================================================

>
>
>> Sent: Tuesday, February 26, 2019 at 6:01 PM
>> From: "Haricophile" <haricophile@???>
>> To: guilde@???
>> Subject: Re: Probleme reseau
>>
>> Le lundi 25 février 2019 à 16:03 +0100, Patrick Dupre a écrit :
>>> Bonjour,
>>>
>>> Question un peu difficile.
>>> Cela fait 15 ans que je travaille avec une fedora, actuellement,
>>> j'ai 3 PC avec des configurations tres similaires. Mais j'ai un
>>> probleme de connection reseau avec le PC qui est dans mon bureau.
>>> Typiquement, lorsque je demarre le PC, je dois attendre ~5 mn
>>> pour avoir la connection reseau, puis je peux perdre celle-ci.
>>> Puis elle peut revenir sans que je comprenne pourquoi.
>>
>> Vérifie quand même soigneusement les RJ45 côté câble et carte, un mauvais
>> contact...
>>
>>
>>
>>
>>
>