[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
Dear Steve, > Some general pointers from reading this... > > Firstly, I don't have much experience of Fedora, I'm an Arch Linux > guy, so there may be some comments here that just don't apply... 😊 Hyperbola is based on Arch, so I'm sure there'll be plenty of topics to discuss in the near future :) > Anyway, as you're already doing... keeping a log of what's happening > is best. Doesn't matter if it's a text file (best) or paper, but... > > What time does it happen What's the status of the links when there was > communication and no communication, by this I mean: > > ping 208.67.222.222 ping resolver1.opendns.com > > (or your choice...) > > Same with your router, if it has a name...? I don't think the router has a name, but thanks for the suggestion. I've written down all those ping results and the network status on a couple of occasions now; those outputs are at least mostly consistent with what I replied to Mr. Meowski with. > Do you have more than one network management service running - systemd > can be interfering with NetworkManager and DNS and timesync > and... and... and... I've attached a list of all the services shown in systemctl list-units; hopefully there's something in there that could be a clue. Is there anything in that list that looks problematic? > Also worth checking is your local computer's health at the > time... maybe use nmon to watch cpu and disk... or maybe nload to > watch the network load I hadn't thought of that! I haven't been using any special tools for that, but since I do have a CPU load indicator on my status bar I can confirm that the CPU is not under any particular load when this happens. Nor does the disk load indicator on the PC case itself show any intense activity. > But... if it's happening fairly frequently, I'd try running a live OS > (unless you want to do an upgrade anyway 😊) and just see if that > magically cures the problem. At least you'll know if it's the local > computer. Then it's your choice to dive in, or wipe away 😉 Are you suggesting that running the Debian live OS for long enough will fix the problem for Fedora? That would be nice if so :D I've just been using Wireshark to see if there are any leads in that direction. I'll come back to it tomorrow when I am not so tired, so don't feel like you have to rush in a response tonight or anything! ZZZzzzz.... Thank you very much for getting involved in this. I appreciate the help! Best wishes, Sebastian -- - Freenode: 'seabass' - Matrix: '@seabass:chat.weho.st' -- The Mailing List for the Devon & Cornwall LUG https://mailman.dcglug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq