On Tue, Sep 7, 2021 at 3:21 PM Tamer Higazi <th9...@googlemail.com> wrote: [...]
> Sep 07 22:15:19 tux systemd[1]: Starting Network Configuration... > Sep 07 22:15:19 tux systemd-networkd[958]: lo: Link UP > Sep 07 22:15:19 tux systemd-networkd[958]: lo: Gained carrier > Sep 07 22:15:19 tux systemd-networkd[958]: Enumeration completed > Sep 07 22:15:19 tux systemd[1]: Started Network Configuration. > Sep 07 22:15:20 tux systemd-networkd[958]: eth0: Interface name change > detected, renamed to enp6s0. > Sep 07 22:15:20 tux systemd-networkd[958]: eth1: Interface name change > detected, renamed to enp7s0. > The message "enp6s0: Link UP" never appears? My log is very similar: Aug 31 17:24:12 graphite systemd[1]: Starting Network Configuration... Aug 31 17:24:12 graphite systemd-networkd[453]: lo: Link UP Aug 31 17:24:12 graphite systemd-networkd[453]: lo: Gained carrier Aug 31 17:24:12 graphite systemd-networkd[453]: Enumeration completed Aug 31 17:24:12 graphite systemd[1]: Started Network Configuration. Aug 31 17:24:12 graphite systemd-networkd[453]: eth0: Interface name change detected, renamed to eno1. Aug 31 17:24:14 graphite systemd-networkd[453]: eno1: Link UP Aug 31 17:24:17 graphite systemd-networkd[453]: eno1: Gained carrier Aug 31 17:24:19 graphite systemd-networkd[453]: eno1: Gained IPv6LL The change from eth0 to eno1 happens *after* "Started Network Configuration", like yours, but my connection goes up immediately. Can you please do me a favour and execute on your machine: > systemctl list-dependencies --after systemd-networkd > > my one outputs this: > > tamer@tux ~ $ systemctl list-dependencies --after systemd-networkd > systemd-networkd.service > ● ├─-.mount > ● ├─system.slice > ● ├─systemd-journald.socket > ● ├─systemd-networkd.socket > ● ├─systemd-sysctl.service > ○ ├─systemd-sysusers.service > ○ ├─systemd-udev-settle.service > ● ├─systemd-udevd.service > ○ └─network-pre.target > Mine is: aztlan ~ # systemctl list-dependencies --after systemd-networkd systemd-networkd.service ● ├─-.mount ● ├─system.slice ● ├─systemd-journald.socket ● ├─systemd-networkd.socket ● ├─systemd-sysctl.service ○ ├─systemd-sysusers.service ● ├─systemd-udevd.service ● └─network-pre.target ○ └─iptables-restore.service In one machine, and kodi ~ # systemctl list-dependencies --after systemd-networkd systemd-networkd.service ● ├─-.mount ● ├─system.slice ● ├─systemd-journald.socket ● ├─systemd-networkd.socket ● ├─systemd-sysctl.service ○ ├─systemd-sysusers.service ● ├─systemd-udevd.service ○ └─network-pre.target In another. The only difference I see is the systemd-udev-settle.service, do you have it enabled it? What systemd-* services do you have enabled? I have: aztlan ~ # find /etc/systemd/system -name "systemd-*" -type l /etc/systemd/system/network-online.target.wants/systemd-networkd-wait-online.service /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service /etc/systemd/system/multi-user.target.wants/systemd-networkd.service /etc/systemd/system/sockets.target.wants/systemd-networkd.socket and kodi ~ # find /etc/systemd/system -name "systemd-*" -type l /etc/systemd/system/sockets.target.wants/systemd-networkd.socket /etc/systemd/system/network-online.target.wants/systemd-networkd-wait-online.service /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service /etc/systemd/system/multi-user.target.wants/systemd-resolved.service /etc/systemd/system/multi-user.target.wants/systemd-networkd.service Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
