madko wrote:Ce n'est pas la même carte réseau sous ta F27 ??
Si si c'est la même carte, je n'en ai pas d'autre.
Pour les autres questions :
# routel
target gateway source proto scope dev tbl
default 192.168.0.1 static enp4s0
192.168.0.0/ 24 192.168.0.3 kernel link enp4s0
127.0.0.0 broadcast 127.0.0.1 kernel link lo local
127.0.0.0/ 8 local 127.0.0.1 kernel host lo local
127.0.0.1 local 127.0.0.1 kernel host lo local
127.255.255.255 broadcast 127.0.0.1 kernel link lo local
192.168.0.0 broadcast 192.168.0.3 kernel link enp4s0 local
192.168.0.3 local 192.168.0.3 kernel host enp4s0 local
192.168.0.255 broadcast 192.168.0.3 kernel link enp4s0 local
::1 kernel lo
fe80::/ 64 kernel enp4s0
::1 local kernel lo local
fe80::213:46ff:fe3c:9d7c local kernel enp4s0 local
ff00::/ 8 enp4s0 local
# ip route
default via 192.168.0.1 dev enp4s0 proto static metric 100
192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.3 metric 100
# systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2018-09-16 19:02:43 CEST; 3min 47s ago
Docs: man:NetworkManager(8)
Main PID: 649 (NetworkManager)
Tasks: 3 (limit: 4915)
Memory: 13.5M
CGroup: /system.slice/NetworkManager.service
└─649 /usr/sbin/NetworkManager --no-daemon
sept. 16 19:02:47 domaine2.domaine.com NetworkManager[649]: <info> [1537117367.6544] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
sept. 16 19:02:47 domaine2.domaine.com NetworkManager[649]: <info> [1537117367.6830] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
sept. 16 19:02:47 domaine2.domaine.com NetworkManager[649]: <info> [1537117367.7353] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
sept. 16 19:02:47 domaine2.domaine.com NetworkManager[649]: <info> [1537117367.7356] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
sept. 16 19:02:47 domaine2.domaine.com NetworkManager[649]: <info> [1537117367.7359] manager: NetworkManager state is now CONNECTED_LOCAL
sept. 16 19:02:47 domaine2.domaine.com NetworkManager[649]: <info> [1537117367.8491] manager: NetworkManager state is now CONNECTED_SITE
sept. 16 19:02:47 domaine2.domaine.com NetworkManager[649]: <info> [1537117367.8493] policy: set 'eth0' (enp4s0) as default for IPv4 routing and DNS
sept. 16 19:02:47 domaine2.domaine.com NetworkManager[649]: <info> [1537117367.9597] device (enp4s0): Activation: successful, device activated.
sept. 16 19:02:47 domaine2.domaine.com NetworkManager[649]: <info> [1537117367.9604] manager: startup complete
sept. 16 19:02:47 domaine2.domaine.com NetworkManager[649]: <info> [1537117367.9610] manager: NetworkManager state is now CONNECTED_GLOBAL
# ethtool -i enp4s0
driver: r8169
version: 2.3LK-NAPI
firmware-version:
expansion-rom-version:
bus-info: 0000:04:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no
# lspci -nnk | grep -iA3 "Ethernet"
04:00.0 Ethernet controller [0200]: D-Link System Inc DGE-528T Gigabit Ethernet Adapter [1186:4300] (rev 10)
Subsystem: D-Link System Inc DGE-528T PCI Gigabit Ethernet Adapter [1186:4300]
Kernel driver in use: r8169
Kernel modules: r8169
04:06.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) [104c:8024]
Je me demande en fait s'il n'y aurait pas un bug dans la compilation du module dans le noyau 4.18. Mystère.