just realized that for some strange reason my ethernet NIC changes from 1Gbit to 100Mbit
anybody has an idea how to fix this behavior? i would like to have 1Gbit within my network, especially due to communication with NAS
root@sidbox:[/home/absolut]# dmesg | grep eth
[ 0.939314] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) d0:50:99:73:d0:74
[ 0.939317] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 0.939349] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
[ 4.083717] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 4.300173] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 7.178634] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 7.178678] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 12.083049] e1000e: eth0 NIC Link is Up 100 Mbps Half Duplex, Flow Control: None
[ 12.083058] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
root@sidbox:[/home/absolut]# ethtool eth0 | grep Speed
Speed: 100Mb/s
just kicked my NIC manually to 1000Mbit with this commend:
ethtool -s eth0 speed 1000 duplex full
originally, that was not required. i wonder why my machine would switch to 100Mbit half duplex at all... :/
anybody able to reproduce?
best
absolut
Problem with your router or switch?
hm, it does not look the router is at fault here... synology NAS reports 1000MBit/s, and the workstation runs also at 1000 (need to check after reboot). maybe the cable?
i'll be testing... for now consider the issue in "monitoring" state...
thanks
absolut
Using e1000 here on a new installation of patience:
root@dibl-patience:/# dmesg | grep enp0s31f6
[ 1.214053] e1000e 0000:00:1f.6 enp0s31f6: renamed from eth0
[ 4.101359] br0: port 1(enp0s31f6) entered blocking state
[ 4.101360] br0: port 1(enp0s31f6) entered disabled state
[ 4.101386] device enp0s31f6 entered promiscuous mode
[ 7.314333] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 7.314382] br0: port 1(enp0s31f6) entered blocking state
[ 7.314382] br0: port 1(enp0s31f6) entered forwarding state
root@dibl-patience:/# ethtool enp0s31f6 | grep Speed
Speed: 1000Mb/s
root@dibl-patience:/#
Seems stable.
some more insights from today below... i think more and more towards the Ethernet cable. need to find a replacement and check it after that
root@sidbox:[/home/absolut]# dmesg | grep eth
[ 0.939314] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) d0:50:99:73:d0:74
[ 0.939317] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 0.939349] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
[ 4.083717] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 4.300173] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 7.178634] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 7.178678] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 12.083049] e1000e: eth0 NIC Link is Up 100 Mbps Half Duplex, Flow Control: None
[ 12.083058] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
[ 311.104061] e1000e: eth0 NIC Link is Down
[ 318.134169] e1000e: eth0 NIC Link is Up 100 Mbps Half Duplex, Flow Control: None
[ 318.134172] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
[ 400.763223] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Best cable for ensuring you get reliable 1000Mbit network speeds are Cat 5e cables, where as the older cat 5 (with no e) just barely support that speed reliably. Also make sure you are using quality made cables and that are not damaged. Hope this helps.