On Fr, 27.11.20 23:18, Gena Makhomed (gmm@xxxxxxxxx) wrote: > How to fix or workaround this problem with default route? Have you looked at networkd's logs? Lennart -- Lennart Poettering, Berlin _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: No default route after "systemctl restart systemd-networkd"
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: No default route after "systemctl restart systemd-networkd"
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Date: Sat, 19 Dec 2020 13:37:31 +0100
- Cc: systemd-devel@xxxxxxxxxxxxxxxxxxxxx
- In-reply-to: <7b0fb8e0-34f3-b0c9-5ad5-980691ac623d@csdoc.com>
- References: <7b0fb8e0-34f3-b0c9-5ad5-980691ac623d@csdoc.com>
- References:
- No default route after "systemctl restart systemd-networkd"
- From: Gena Makhomed
- No default route after "systemctl restart systemd-networkd"
- Prev by Date: Re: Why is journalctl -b so slow?
- Next by Date: Re: Mount options for ESP, LUKS and rootfs in automatic partition discovery and mounting
- Previous by thread: No default route after "systemctl restart systemd-networkd"
- Next by thread: Mount options for ESP, LUKS and rootfs in automatic partition discovery and mounting
- Index(es):
 |