On 4/4/22 8:38 am, Dmitry Katsubo wrote:
I recently went through something similar where networking.service got obscure errors I couldn't diagnose.Dear Debian community,I've exercised several directions to solve the issue, however I've failed. Would be great if somebody can share his idea. After upgrading from Debian buster to bullseye I still have the same issue: # systemctl status networking.service — networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2022-04-04 00:37:29 CEST; 31min ago Docs: man:interfaces(5) Process: 1287 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE) Main PID: 1287 (code=exited, status=1/FAILURE) CPU: 83ms
I went against my better judgement and changed to using systemd-networkd.service
Rather surprisingly I got a working network with no errors. You could try that approach and see if you have any luck. When you switch, you need to backup /etc/network/interfaces and copy /etc/network/interfaces.default over /etc/network/interfaces.
I remain perplexed however why there are at least three different mostly incompatible network management systems :
* systemd.networkd.service * networking.service * NetworkManager.service -- Jeremy
OpenPGP_signature
Description: OpenPGP digital signature