-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, Jan 21, 2016 at 01:48:40PM +0200, David Baron wrote: > Royal pain in the ... > What do I do about this? > > (Saw something about network manager/netcfg conflict but I do not have > netcfg.)
What have the system logs (dmesg, /var/log/syslog, /var/log/messages -- or whatever equivalent there is in the systemd world) to say? Perhaps you can find a correlation between the (dis)connects and some log activity? Sometimes a flakey cable (they *do* exist) or flakey network hardware show such symptoms. To give you an idea of what to watch out for, I just did tomas@rasputin:~$ sudo tail -f /var/log/messages and then pulled my eth cable out of the laptop and re-inserted it. This is what the log shows: Jan 21 12:59:44 rasputin kernel: [14423.324311] r8169 0000:02:00.0 eth0: link down Jan 21 12:59:47 rasputin kernel: [14426.188524] r8169 0000:02:00.0 eth0: link up But of course, NetworkManager has been seen acting up too, from time to time (the last time it did it for me it got a perpetual ban from my boxen, but that's a while back. Reportedly, it got better). regards - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlagwSUACgkQBcgs9XrR2karxACeO5vzhnNlGdza4jO44IWfqzKp R7QAn1vvnnX1ntn8hYozD8jvlsRAmRMR =vnlX -----END PGP SIGNATURE-----
