Am 05.07.2015 um 20:52 schrieb Gordon Messmer: > On 07/05/2015 07:57 AM, Meikel wrote: >> Jul 5 16:36:08 meikel-pc kernel: ADDRCONF(NETDEV_UP): eth0: link is not >> ready >> Jul 5 16:36:23 meikel-pc kernel: ADDRCONF(NETDEV_CHANGE): eth0: link >> becomes ready >> >> It takes 15 seconds between the two messages until it becomes ready. I >> have no idea why it first says that the link is not ready. > > It's probably autonegotiation of link speed. I'm not sure why it'd > take that long. I'd think the most likely explanation would be a bad > cable. Could also be a flaky port on the switch, or a flaky Ethernet > card. What brand is the local interface? > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > > I'll check the cable (not clear how I can do that, probably using another cable and connecting to another outlet). I think the local interface is directly integrated into the Intel Desktop Board DH87RL. dmesg | grep eth e1000e 0000:00:19.0: eth0: registered PHC clock e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:22:4d:b0:e0:e1 e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection e1000e 0000:00:19.0: eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF ADDRCONF(NETDEV_UP): eth0: link is not ready e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None e1000e 0000:00:19.0: eth0: 10/100 speed: disabling TSO ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready eth0: no IPv6 routers present lspci | grep Ether 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04) It says that it has a speed of 10/100, but I definitely expect 1000 Mbps!