ToddAndMargo via users writes:
Hi All,Fedora 41 I have a customer I set up a Fedora 41 server. Problem: about once a week, its networking dies. All network services are dead, xrdp, ssh, samba, etc.. All of them. Console logins work fine. The solution is to call the customer and have him log in at the console and issue a shutdown. On power up, all work again. What I would like to do, is to set up a cron job to test the networking (ping firewall) and restart/correct the network if I find it down. Now I do know about # systemctl restart systemd-networkd.service But is that enough?
Well? You tell us. Does doing this regain network connectivity, for the problem child in question?
What do I need to do to
put the network into the same state as after
a fresh reboot?
Well, that really depends on why it's not in a fresh state, to start with. All you know is "it doesn't work". Without knowing the root cause of a busted network connection any advice is just a random, worthless guess.
It could be anything from a broken DHCP server, on the network, refusing to renew the client lease, to a dodgy network card that randomly takes a power, and requires a reboot cycle and a kick in the ass from the kernel, to wake up. It goes without saying that the solution to one would be vastly different than the solution to the other, if a solution is even possible.
pgpxSVj6ff01q.pgp
Description: PGP signature
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
