Dear Dr. Valdés,
I am sorry to tell you that the result still remains the same.
I am also not a systemd expert....
but somebody in the mailing list told me, that the "order" of process
might not be right ?
url: https://github.com/systemd/systemd/issues/7293
best, Tamer Higazi
● systemd-networkd.service - Network Configuration
Loaded: loaded (/lib/systemd/system/systemd-networkd.service;
enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/systemd-networkd.service.d
└─override.conf
Active: active (running) since Tue 2021-09-07 19:54:00 CEST; 1min
45s ago
TriggeredBy: ● systemd-networkd.socket
Docs: man:systemd-networkd.service(8)
Main PID: 957 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 19136)
Memory: 2.3M
CGroup: /system.slice/systemd-networkd.service
└─957 /lib/systemd/systemd-networkd
Sep 07 19:54:00 tux systemd[1]: Starting Network Configuration...
Sep 07 19:54:00 tux systemd-networkd[957]: lo: Link UP
Sep 07 19:54:00 tux systemd-networkd[957]: lo: Gained carrier
Sep 07 19:54:00 tux systemd-networkd[957]: Enumeration completed
Sep 07 19:54:00 tux systemd[1]: Started Network Configuration.
Sep 07 19:54:01 tux systemd-networkd[957]: eth0: Interface name change
detected, renamed to enp6s0.
Sep 07 19:54:01 tux systemd-networkd[957]: eth1: Interface name change
detected, renamed to enp7s0.
Am 9/7/21 um 4:11 AM schrieb Canek Peláez Valdés:
On Mon, Sep 6, 2021 at 2:46 PM Tamer Higazi <th9...@googlemail.com
<mailto:th9...@googlemail.com>> wrote:
[...]
/etc/systemd/network/20-wirded.network:
[...]
That looks fine to me.
for enp7s0 there is no other network file.
That is as it should be.
I think with THIS systemd version, the whole problem is, that the
configuration will be done before the devices are made and renamed to
enp6s0 and enp7s0.
I don't think so; the renaming of ethernet devices happens really
early, and systemd-networkd detects it automatically (journal -b -g
enp6s0 should show "enp6s0: renamed from eth0" as first log line, and
then systemd-networkd detecting it).
The problem is, how to solve it ....
Try adding this to /etc/systemd/network/20-wirded.network, at the end:
[Link]
RequiredForOnline=false
but this is a workaround; everything should work automagically.
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
