Issue when rebooting Yunohost: manually running "dhclient" is required to recover connectivity

, ,

My YunoHost server

Hardware: x86 microcomputer, Intel Celeron N4100
YunoHost version: 11.0.4+202202091700 over Debian 11 Bullseye
I have access to my server : Through SSH, webadmin, and direct access
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : yes
If yes, please explain: Currently running Debian 11 Bullseye. The hardware by default didn’t detect the Ethernet port, so the Debian installer added the r8168-dkms module.

Description of my issue

Whenever I need to reboot my device (due to hardware failure or a blackout), it always starts without Ethernet connectivity. After some trial and error, I found that I must manually execute dhclient directly from the hardware in order for the connectivity to return - otherwise, not even SSH will be accessible. This might be related to the fact that the device requires a DKMS driver to handle Ethernet. Oddly enough, the problem only occurred after I tested installing a GUI (LXQT) and then uninstalled it - LXQT apparently ships with its own network manager and it might have altered some configuration uncleanly.

Relevant messages from dmesg:

[    3.356024] ACPI Error: No handler for Region [ECF2] (000000002d670e5c) [EmbeddedControl] (20200925/evregion-129)
[    3.356091] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20200925/exfldio-261)
[    3.356144] ACPI Error: Aborting method \_SB.PCI0.SBRG.H_EC.BAT0._STA due to previous error (AE_NOT_EXIST) (20200925/psparse-529)

(This one comes out immediately after running dhclient -v)

[   44.713184] eno1: 0xffffbdc900059000, 50:a1:32:0a:c0:c8, IRQ 124
[   48.885133] r8168: eno1: link up
[   48.885811] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.