Hello.
I’m running Leap 15.5 on my computer. When I’m working on the computer the network sometimes disconnects and connects again multiple times. This happens irregularly and I cannot reproduce it. Does anyone have an idea how I could approach this problem?
Thanks for your help.
Not me, but you could help by giving some more information like cable/wifi, router, how you detect the “disconnects and connects again multiple times”, etc.
I have a local network with five different computers connected to it. The IP addresses of the computers have local IP’s 192.168.1.100/24 to 192.168.1.105/24. They are connected to a switch and the switch is connected to router from the internet provider.All the computers are running with Leap 15.5.
I detect the “disconnects and connects” by popup messages from the network icon which is located at the right hand side of the KDE menu bar. When it disconnects the message “network deactivated” pops up and after a few seconds the message “network activates” pops up and after a few seconds the procedure repeats itself 5 or 6 times. Then the network is sometimes stable again for several hours before it happens again. It normally happens after the system startup and then it is stable for a certain time and then it happens again. It is really on a irregular basis and I cannot reproduce it.
In /var/log/messages I can see message like this
2023-12-02T11:35:50.021151+01:00 sh avahi-daemon[788]: Withdrawing address record for 192.168.1.106 on eth0.
2023-12-02T11:35:50.021252+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.106.
2023-12-02T11:35:50.021312+01:00 sh avahi-daemon[788]: Interface eth0.IPv4 no longer relevant for mDNS.
2023-12-02T11:35:50.021441+01:00 sh avahi-daemon[788]: Withdrawing address record for 2a02:1210:7489:a300:d091:ac91:c81a:ce00 on eth0.
2023-12-02T11:35:50.021550+01:00 sh avahi-daemon[788]: Withdrawing address record for 2a02:1210:7489:a300:e284:205d:22b6:9db1 on eth0.
2023-12-02T11:35:50.021668+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv6 with address 2a02:1210:7489:a300:e284:205d:22b6:9db1.
2023-12-02T11:35:50.021718+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:35:50.021769+01:00 sh avahi-daemon[788]: Registering new address record for fe80::1744:cadf:be2:4aee on eth0..
2023-12-02T11:35:50.021854+01:00 sh avahi-daemon[788]: Withdrawing address record for fe80::1744:cadf:be2:4aee on eth0.
2023-12-02T11:35:50.021904+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:35:50.021964+01:00 sh avahi-daemon[788]: Interface eth0.IPv6 no longer relevant for mDNS.
2023-12-02T11:35:57.592018+01:00 sh kernel: [12847.165336][T18271] igc 0000:01:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2023-12-02T11:35:57.725814+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.106.
2023-12-02T11:35:57.725950+01:00 sh avahi-daemon[788]: New relevant interface eth0.IPv4 for mDNS.
2023-12-02T11:35:57.726001+01:00 sh avahi-daemon[788]: Registering new address record for 192.168.1.106 on eth0.IPv4.
2023-12-02T11:35:57.726927+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:35:57.726975+01:00 sh avahi-daemon[788]: New relevant interface eth0.IPv6 for mDNS.
2023-12-02T11:35:57.727012+01:00 sh avahi-daemon[788]: Registering new address record for fe80::1744:cadf:be2:4aee on eth0..
2023-12-02T11:36:04.050377+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:36:04.050466+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv6 with address 2a02:1210:7489:a300:e284:205d:22b6:9db1.
2023-12-02T11:36:04.050602+01:00 sh avahi-daemon[788]: Registering new address record for 2a02:1210:7489:a300:e284:205d:22b6:9db1 on eth0..
2023-12-02T11:36:04.050664+01:00 sh avahi-daemon[788]: Withdrawing address record for fe80::1744:cadf:be2:4aee on eth0.
2023-12-02T11:36:05.197671+01:00 sh avahi-daemon[788]: Registering new address record for 2a02:1210:7489:a300:8292:4469:e956:c7bf on eth0..
2023-12-02T11:36:14.100067+01:00 sh kernel: [12863.673053][T18772] igc 0000:01:00.0 eth0: NIC Link is Down
2023-12-02T11:36:17.812135+01:00 sh kernel: [12867.385326][T19059] igc 0000:01:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2023-12-02T11:36:29.428081+01:00 sh kernel: [12879.000761][T19852] igc 0000:01:00.0 eth0: NIC Link is Down
2023-12-02T11:36:33.560108+01:00 sh kernel: [12883.132873][T19852] igc 0000:01:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2023-12-02T11:36:33.576213+01:00 sh kernel: [12883.148590][T19852] igc 0000:01:00.0 eth0: NIC Link is Down
2023-12-02T11:36:37.696068+01:00 sh kernel: [12887.268714][T19852] igc 0000:01:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2023-12-02T11:36:37.812115+01:00 sh kernel: [12887.384743][T19852] igc 0000:01:00.0 eth0: NIC Link is Down
2023-12-02T11:36:41.940086+01:00 sh kernel: [12891.512686][T19852] igc 0000:01:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2023-12-02T11:36:56.768080+01:00 sh kernel: [12906.340106][T18772] igc 0000:01:00.0 eth0: NIC Link is Down
2023-12-02T11:37:00.484110+01:00 sh kernel: [12910.056302][T18271] igc 0000:01:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2023-12-02T11:37:00.612241+01:00 sh kernel: [12910.183946][T19852] igc 0000:01:00.0 eth0: NIC Link is Down
2023-12-02T11:37:04.316124+01:00 sh kernel: [12913.888089][T19852] igc 0000:01:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2023-12-02T11:38:52.384061+01:00 sh kernel: [13021.953322][T18799] igc 0000:01:00.0 eth0: NIC Link is Down
2023-12-02T11:38:56.600063+01:00 sh kernel: [13026.169431][T18271] igc 0000:01:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2023-12-02T11:39:50.656074+01:00 sh kernel: [13080.223866][T20651] igc 0000:01:00.0 eth0: NIC Link is Down
2023-12-02T11:39:54.796101+01:00 sh kernel: [13084.364053][T20651] igc 0000:01:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2023-12-02T11:39:55.312096+01:00 sh kernel: [13084.879694][T14580] igc 0000:01:00.0 eth0: NIC Link is Down
2023-12-02T11:40:02.052799+01:00 sh avahi-daemon[788]: Withdrawing address record for 192.168.1.106 on eth0.
2023-12-02T11:40:02.052946+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.106.
2023-12-02T11:40:02.053018+01:00 sh avahi-daemon[788]: Interface eth0.IPv4 no longer relevant for mDNS.
2023-12-02T11:40:02.053163+01:00 sh avahi-daemon[788]: Withdrawing address record for 2a02:1210:7489:a300:8292:4469:e956:c7bf on eth0.
2023-12-02T11:40:02.053455+01:00 sh avahi-daemon[788]: Withdrawing address record for 2a02:1210:7489:a300:e284:205d:22b6:9db1 on eth0.
2023-12-02T11:40:02.053538+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv6 with address 2a02:1210:7489:a300:e284:205d:22b6:9db1.
2023-12-02T11:40:02.053628+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:40:02.053689+01:00 sh avahi-daemon[788]: Registering new address record for fe80::1744:cadf:be2:4aee on eth0..
2023-12-02T11:40:02.053753+01:00 sh avahi-daemon[788]: Withdrawing address record for fe80::1744:cadf:be2:4aee on eth0.
2023-12-02T11:40:02.053818+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:40:02.053881+01:00 sh avahi-daemon[788]: Interface eth0.IPv6 no longer relevant for mDNS.
2023-12-02T11:40:03.776045+01:00 sh kernel: [13093.343751][T20651] igc 0000:01:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2023-12-02T11:40:03.808019+01:00 sh kernel: [13093.375456][T18772] igc 0000:01:00.0 eth0: NIC Link is Down
2023-12-02T11:40:03.923538+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.106.
2023-12-02T11:40:03.923619+01:00 sh avahi-daemon[788]: New relevant interface eth0.IPv4 for mDNS.
2023-12-02T11:40:03.923663+01:00 sh avahi-daemon[788]: Registering new address record for 192.168.1.106 on eth0.IPv4.
2023-12-02T11:40:03.924849+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:40:03.924929+01:00 sh avahi-daemon[788]: New relevant interface eth0.IPv6 for mDNS.
2023-12-02T11:40:03.924976+01:00 sh avahi-daemon[788]: Registering new address record for fe80::1744:cadf:be2:4aee on eth0..
2023-12-02T11:40:07.536076+01:00 sh kernel: [13097.103741][T19855] igc 0000:01:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2023-12-02T11:40:07.548128+01:00 sh kernel: [13097.115440][T19852] igc 0000:01:00.0 eth0: NIC Link is Down
2023-12-02T11:40:14.817146+01:00 sh avahi-daemon[788]: Withdrawing address record for 192.168.1.106 on eth0.
2023-12-02T11:40:14.817262+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.106.
2023-12-02T11:40:14.817331+01:00 sh avahi-daemon[788]: Interface eth0.IPv4 no longer relevant for mDNS.
2023-12-02T11:40:14.817577+01:00 sh avahi-daemon[788]: Withdrawing address record for fe80::1744:cadf:be2:4aee on eth0.
2023-12-02T11:40:14.817656+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:40:14.817724+01:00 sh avahi-daemon[788]: Interface eth0.IPv6 no longer relevant for mDNS.
2023-12-02T11:40:16.396249+01:00 sh kernel: [13105.963478][T18271] igc 0000:01:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2023-12-02T11:40:16.675677+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.106.
2023-12-02T11:40:16.675823+01:00 sh avahi-daemon[788]: New relevant interface eth0.IPv4 for mDNS.
2023-12-02T11:40:16.675915+01:00 sh avahi-daemon[788]: Registering new address record for 192.168.1.106 on eth0.IPv4.
2023-12-02T11:40:16.677810+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:40:16.678118+01:00 sh avahi-daemon[788]: New relevant interface eth0.IPv6 for mDNS.
2023-12-02T11:40:16.678242+01:00 sh avahi-daemon[788]: Registering new address record for fe80::1744:cadf:be2:4aee on eth0..
2023-12-02T11:40:21.220112+01:00 sh kernel: [13110.787088][T19852] igc 0000:01:00.0 eth0: NIC Link is Down
2023-12-02T11:40:27.389940+01:00 sh avahi-daemon[788]: Withdrawing address record for 192.168.1.106 on eth0.
2023-12-02T11:40:27.390042+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.106.
2023-12-02T11:40:27.390084+01:00 sh avahi-daemon[788]: Interface eth0.IPv4 no longer relevant for mDNS.
2023-12-02T11:40:27.390120+01:00 sh avahi-daemon[788]: Withdrawing address record for fe80::1744:cadf:be2:4aee on eth0.
2023-12-02T11:40:27.390177+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:40:27.390236+01:00 sh avahi-daemon[788]: Interface eth0.IPv6 no longer relevant for mDNS.
2023-12-02T11:40:34.758283+01:00 sh kernel: [13124.327085][T18271] igc 0000:01:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2023-12-02T11:40:34.901517+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.106.
2023-12-02T11:40:34.901657+01:00 sh avahi-daemon[788]: New relevant interface eth0.IPv4 for mDNS.
2023-12-02T11:40:34.901704+01:00 sh avahi-daemon[788]: Registering new address record for 192.168.1.106 on eth0.IPv4.
2023-12-02T11:40:34.902457+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:40:34.902541+01:00 sh avahi-daemon[788]: New relevant interface eth0.IPv6 for mDNS.
2023-12-02T11:40:34.902600+01:00 sh avahi-daemon[788]: Registering new address record for fe80::1744:cadf:be2:4aee on eth0..
2023-12-02T11:40:41.242489+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:40:41.242588+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv6 with address 2a02:1210:7489:a300:e284:205d:22b6:9db1.
2023-12-02T11:40:41.242949+01:00 sh avahi-daemon[788]: Registering new address record for 2a02:1210:7489:a300:e284:205d:22b6:9db1 on eth0..
2023-12-02T11:40:41.243143+01:00 sh avahi-daemon[788]: Withdrawing address record for fe80::1744:cadf:be2:4aee on eth0.
2023-12-02T11:40:42.732740+01:00 sh avahi-daemon[788]: Registering new address record for 2a02:1210:7489:a300:9cd8:f115:4741:6fc4 on eth0..
2023-12-02T11:40:59.568104+01:00 sh kernel: [13149.135398][T18772] igc 0000:01:00.0 eth0: NIC Link is Down
2023-12-02T11:41:05.719554+01:00 sh avahi-daemon[788]: Withdrawing address record for 192.168.1.106 on eth0.
2023-12-02T11:41:05.719657+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.106.
2023-12-02T11:41:05.719711+01:00 sh avahi-daemon[788]: Interface eth0.IPv4 no longer relevant for mDNS.
2023-12-02T11:41:05.719759+01:00 sh avahi-daemon[788]: Withdrawing address record for 2a02:1210:7489:a300:9cd8:f115:4741:6fc4 on eth0.
2023-12-02T11:41:05.719842+01:00 sh avahi-daemon[788]: Withdrawing address record for 2a02:1210:7489:a300:e284:205d:22b6:9db1 on eth0.
2023-12-02T11:41:05.719900+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv6 with address 2a02:1210:7489:a300:e284:205d:22b6:9db1.
2023-12-02T11:41:05.719958+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:41:05.720017+01:00 sh avahi-daemon[788]: Registering new address record for fe80::1744:cadf:be2:4aee on eth0..
2023-12-02T11:41:05.720111+01:00 sh avahi-daemon[788]: Withdrawing address record for fe80::1744:cadf:be2:4aee on eth0.
2023-12-02T11:41:05.720171+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:41:05.720224+01:00 sh avahi-daemon[788]: Interface eth0.IPv6 no longer relevant for mDNS.
2023-12-02T11:41:07.948127+01:00 sh kernel: [13157.515376][T20651] igc 0000:01:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2023-12-02T11:41:08.206730+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.106.
2023-12-02T11:41:08.206810+01:00 sh avahi-daemon[788]: New relevant interface eth0.IPv4 for mDNS.
2023-12-02T11:41:08.206857+01:00 sh avahi-daemon[788]: Registering new address record for 192.168.1.106 on eth0.IPv4.
2023-12-02T11:41:08.208731+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:41:08.208819+01:00 sh avahi-daemon[788]: New relevant interface eth0.IPv6 for mDNS.
2023-12-02T11:41:08.208866+01:00 sh avahi-daemon[788]: Registering new address record for fe80::1744:cadf:be2:4aee on eth0..
2023-12-02T11:41:08.644067+01:00 sh kernel: [13158.211121][T19852] igc 0000:01:00.0 eth0: NIC Link is Down
2023-12-02T11:41:15.123447+01:00 sh avahi-daemon[788]: Withdrawing address record for 192.168.1.106 on eth0.
2023-12-02T11:41:15.123529+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.106.
2023-12-02T11:41:15.123577+01:00 sh avahi-daemon[788]: Interface eth0.IPv4 no longer relevant for mDNS.
2023-12-02T11:41:15.123652+01:00 sh avahi-daemon[788]: Withdrawing address record for fe80::1744:cadf:be2:4aee on eth0.
2023-12-02T11:41:15.123696+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:41:15.123738+01:00 sh avahi-daemon[788]: Interface eth0.IPv6 no longer relevant for mDNS.
2023-12-02T11:41:16.500046+01:00 sh kernel: [13166.067125][T19855] igc 0000:01:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2023-12-02T11:41:16.544025+01:00 sh kernel: [13166.110874][T14580] igc 0000:01:00.0 eth0: NIC Link is Down
2023-12-02T11:41:16.639212+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.106.
2023-12-02T11:41:16.639296+01:00 sh avahi-daemon[788]: New relevant interface eth0.IPv4 for mDNS.
2023-12-02T11:41:16.639344+01:00 sh avahi-daemon[788]: Registering new address record for 192.168.1.106 on eth0.IPv4.
2023-12-02T11:41:16.640686+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:41:16.640773+01:00 sh avahi-daemon[788]: New relevant interface eth0.IPv6 for mDNS.
2023-12-02T11:41:16.640822+01:00 sh avahi-daemon[788]: Registering new address record for fe80::1744:cadf:be2:4aee on eth0..
2023-12-02T11:41:20.680053+01:00 sh kernel: [13170.247186][T19852] igc 0000:01:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2023-12-02T11:41:20.700077+01:00 sh kernel: [13170.266776][T18772] igc 0000:01:00.0 eth0: NIC Link is Down
2023-12-02T11:41:27.850806+01:00 sh avahi-daemon[788]: Withdrawing address record for 192.168.1.106 on eth0.
2023-12-02T11:41:27.850894+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.106.
2023-12-02T11:41:27.850952+01:00 sh avahi-daemon[788]: Interface eth0.IPv4 no longer relevant for mDNS.
2023-12-02T11:41:27.851038+01:00 sh avahi-daemon[788]: Withdrawing address record for fe80::1744:cadf:be2:4aee on eth0.
2023-12-02T11:41:27.851086+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:41:27.851133+01:00 sh avahi-daemon[788]: Interface eth0.IPv6 no longer relevant for mDNS.
2023-12-02T11:41:29.032017+01:00 sh kernel: [13178.598853][T19852] igc 0000:01:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2023-12-02T11:41:29.167637+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.106.
2023-12-02T11:41:29.167736+01:00 sh avahi-daemon[788]: New relevant interface eth0.IPv4 for mDNS.
2023-12-02T11:41:29.167787+01:00 sh avahi-daemon[788]: Registering new address record for 192.168.1.106 on eth0.IPv4.
2023-12-02T11:41:29.168917+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:41:29.169134+01:00 sh avahi-daemon[788]: New relevant interface eth0.IPv6 for mDNS.
2023-12-02T11:41:29.169183+01:00 sh avahi-daemon[788]: Registering new address record for fe80::1744:cadf:be2:4aee on eth0..
2023-12-02T11:41:34.618090+01:00 sh avahi-daemon[788]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::1744:cadf:be2:4aee.
2023-12-02T11:41:34.618275+01:00 sh avahi-daemon[788]: Joining mDNS multicast group on interface eth0.IPv6 with address 2a02:1210:7489:a300:e284:205d:22b6:9db1.
2023-12-02T11:41:34.618319+01:00 sh avahi-daemon[788]: Registering new address record for 2a02:1210:7489:a300:e284:205d:22b6:9db1 on eth0..
2023-12-02T11:41:34.618357+01:00 sh avahi-daemon[788]: Withdrawing address record for fe80::1744:cadf:be2:4aee on eth0.
2023-12-02T11:41:36.013415+01:00 sh avahi-daemon[788]: Registering new address record for 2a02:1210:7489:a300:1d8d:6bb3:62df:7dad on eth0..
2023-12-02T11:47:48.028061+01:00 sh kernel: [13557.583921][T19852] igc 0000:01:00.0 eth0: NIC Link is Down
2023-12-02T11:47:52.192108+01:00 sh kernel: [13561.748067][T22499] igc 0000:01:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2023-12-02T11:47:52.676053+01:00 sh kernel: [13562.231725][T22499] igc 0000:01:00.0 eth0: NIC Link is Down
The logs from the router don’t indicate anything
The only relevant line in this badly readable flood of text is
2023-12-02T11:36:14.100067+01:00 sh kernel: [12863.673053][T18772] igc 0000:01:00.0 eth0: NIC Link is Down
Everything else is the natural consequence of the link loss. It could be driver, it could be NIC firmware, it could be cable, it could be switch port or firmware.
I assume you have this problem on just one of them because you always talked about single computer. In this case the obvious first step is to connect the system with this problem to another switch port where another system is connected using its cable. This will rule out switch and cable.
I have it on all computer where I have Leap 15.5 installed, but if other people connect their Windows machines to the network they have stable connections without interruptions. The Leap 15.5 machines have all different network card hardware.
Then you need to look for the similarities in your Leap systems and the differences with your Windows systems. The problem is that driver loses link. It is way below any application layer. Also - do you connect your Windows system to the same switch port as Linux system using the same cable?
The logs you posted show that driver negotiates 2.5Gbps speed. Does your switch actually support it? What speed Windows systems use? Check on the switch - any difference in port states between Linux and Windows systems?
They still may be using the same underlying chipset and driver.
You could try forcing driver to advertise only 1000Mbps as supported speed
ethtool -s eth0 advertise 0x020
Yes. The windows System is connected to the exact same switch and with the same cables. I already tried replacing all cables, but that didn’t change anything.
The hardware on the system where the log is coming from has a 2.5Gbps port and the switch does even support 10Gbps. The windows system also supports 2.5Gbps. The computer with the Windows system has a dual boot (Leap 15.5 and Windows). If I run Windows on it then there are no interruptions, but if I run Leap 15.5 on it then it has this network “deactivated” and “activated” problem.
Here is the hardware info of the system:
# inxi -Fxz
System:
Kernel: 5.14.21-150500.55.36-default arch: x86_64 bits: 64 compiler: gcc
v: 7.5.0 Console: pty pts/13 Distro: openSUSE Leap 15.5
Machine:
Type: Desktop System: Shuttle product: DS20U v: 1.0 serial: N/A
Mobo: Shuttle model: DS20U v: 1.0 serial: N/A UEFI: American Megatrends
v: 2.03 date: 03/15/2023
Battery:
Device-1: hidpp_battery_0 model: Logitech MX Keys Wireless Keyboard
charge: 100% (should be ignored) status: discharging
CPU:
Info: quad core model: Intel Core i7-10510U bits: 64 type: MT MCP
arch: Comet/Whiskey Lake note: check rev: C cache: L1: 256 KiB L2: 1024 KiB
L3: 8 MiB
Speed (MHz): avg: 701 high: 714 min/max: 400/4900 cores: 1: 714 2: 700
3: 700 4: 700 5: 700 6: 700 7: 700 8: 700 bogomips: 36799
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel CometLake-U GT2 [UHD Graphics] vendor: Holco Enterprise Co
/Shuttle driver: i915 v: kernel arch: Gen-9.5 bus-ID: 00:02.0
Display: x11 server: X.Org v: 1.21.1.4 with: Xwayland v: 22.1.5 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915
resolution: 3840x2160~60Hz
API: OpenGL v: 4.6 Mesa 22.3.5 renderer: Mesa Intel UHD Graphics (CML GT2)
direct render: Yes
Audio:
Device-1: Intel Comet Lake PCH-LP cAVS vendor: Holco Enterprise Co /Shuttle
driver: snd_hda_intel bus-ID: 1-1:2 v: kernel bus-ID: 00:1f.3
Device-2: Plantronics Plantronics Blackwire 5220 Series type: USB
driver: plantronics,snd-usb-audio,usbhid
Sound API: ALSA v: k5.14.21-150500.55.36-default running: yes
Sound Server-1: PulseAudio v: 15.0 running: yes
Sound Server-2: PipeWire v: 0.3.64 running: yes
Network:
Device-1: Intel Ethernet I219-LM vendor: Holco Enterprise Co /Shuttle
driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6
IF: eth1 state: down mac: <filter>
Device-2: Intel Ethernet I225-V vendor: Holco Enterprise Co /Shuttle
driver: igc v: kernel port: N/A bus-ID: 01:00.0
IF: eth0 state: up speed: 2500 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 1.82 TiB used: 174.46 GiB (9.4%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 990 PRO 2TB size: 1.82 TiB
temp: 45.9 C
Partition:
ID-1: / size: 1.82 TiB used: 174.45 GiB (9.4%) fs: btrfs dev: /dev/nvme0n1p2
ID-2: /boot/efi size: 511 MiB used: 5.1 MiB (1.0%) fs: vfat
dev: /dev/nvme0n1p1
ID-3: /home size: 1.82 TiB used: 174.45 GiB (9.4%) fs: btrfs
dev: /dev/nvme0n1p2
ID-4: /opt size: 1.82 TiB used: 174.45 GiB (9.4%) fs: btrfs
dev: /dev/nvme0n1p2
ID-5: /tmp size: 1.82 TiB used: 174.45 GiB (9.4%) fs: btrfs
dev: /dev/nvme0n1p2
ID-6: /var size: 1.82 TiB used: 174.45 GiB (9.4%) fs: btrfs
dev: /dev/nvme0n1p2
Swap:
ID-1: swap-1 type: partition size: 2 GiB used: 0 KiB (0.0%)
dev: /dev/nvme0n1p3
Sensors:
System Temperatures: cpu: 39.0 C pch: 40.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 381 Uptime: 22h 3m Memory: 62.55 GiB used: 12.82 GiB (20.5%)
Init: systemd target: graphical (5) Compilers: gcc: 10.4.0 Packages: 7
note: see --rpm Shell: Bash v: 4.4.23 inxi: 3.3.23
Please post terminal output with the preformatted text button </> !
Sorry about that. I will do that in future posts.
I still have the same problem. Here the output from:
# journalctl -u NetworkManager -f
Dec 06 09:11:46 sh NetworkManager[919]: <info> [1701850306.1141] device (eth0): carrier: link connected
Dec 06 09:11:46 sh NetworkManager[919]: <info> [1701850306.1143] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Dec 06 09:11:46 sh NetworkManager[919]: <info> [1701850306.1151] policy: auto-activating connection 'eth0' (7ba00b1d-8cdd-30da-91ad-bb83ed4f7474)
Dec 06 09:11:46 sh NetworkManager[919]: <info> [1701850306.1156] device (eth0): Activation: starting connection 'eth0' (7ba00b1d-8cdd-30da-91ad-bb83ed4f7474)
Dec 06 09:11:46 sh NetworkManager[919]: <info> [1701850306.1157] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Dec 06 09:11:46 sh NetworkManager[919]: <info> [1701850306.1158] manager: NetworkManager state is now CONNECTING
Dec 06 09:11:46 sh NetworkManager[919]: <info> [1701850306.1160] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dec 06 09:11:46 sh NetworkManager[919]: <info> [1701850306.1356] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Dec 06 09:11:46 sh NetworkManager[919]: <info> [1701850306.1362] policy: set 'eth0' (eth0) as default for IPv4 routing and DNS
Dec 06 09:11:46 sh NetworkManager[919]: <info> [1701850306.2509] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Dec 06 09:11:46 sh NetworkManager[919]: <info> [1701850306.2598] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Dec 06 09:11:46 sh NetworkManager[919]: <info> [1701850306.2600] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Dec 06 09:11:46 sh NetworkManager[919]: <info> [1701850306.2604] manager: NetworkManager state is now CONNECTED_SITE
Dec 06 09:11:46 sh NetworkManager[919]: <info> [1701850306.2606] device (eth0): Activation: successful, device activated.
What does this message tell me?
state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
It tells you that link was detected again and NM started to bring up the interface.
Why is it disconnecting/connecting randomly?
I am afraid I cannot add anything to what I said earlier, at least without some new information.
What kind of information can I provide to further clarify it?
Intel NIC chips have different troubles.
Possibly they’ve been solved in Windows by updated drivers. For Leap you need newer kernel. Try to use Tumbleweed. Test system using NIC with Realtek chip.