Maybe, maybe not.

Typically I have had to do a stop(instead of a restart) then a
modprobe -r <networkmodulename> ; sleep 1 ; modprobe
<networkmodulename> ; then restart.

That works unless the NIC itself has a serious firmware issue and
locks up and really needs a hardware reset that comes on a complete
reboot.

On Sat, Apr 5, 2025 at 7:04 PM ToddAndMargo via users
<[email protected]> wrote:
>
> 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?  What do I need to do to
> put the network into the same state as after
> a fresh reboot?
>
> Many thanks,
> -T
>
>
>
> --
> _______________________________________________
> users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> 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/[email protected]
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
-- 
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to