Forum: >>> Magnum BBS <<<

[gentoo-user] network do not come up after booting, only manual reloadi

From Tamer Higazi@21:1/5 to All on Sun Sep 5 09:50:02 2021

Hi people,

After upgrading my gentoo box i see a new behavior, that my machine
after boot doen't configure my network. My network is configured through systemd-network,

Only if I manually after login execute: "systemctl restart
systemd-network" it gets configured.
Can somebody tell me why this is the case and how to fix it ?

systemctl Logs:

after start:

● systemd-networkd.service - Network Configuration
     Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2021-09-04 08:49:48 CEST; 1min
4s 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 04 08:49:48 tux systemd[1]: Starting Network Configuration...
Sep 04 08:49:48 tux systemd-networkd[957]: lo: Link UP
Sep 04 08:49:48 tux systemd-networkd[957]: lo: Gained carrier
Sep 04 08:49:48 tux systemd-networkd[957]: Enumeration completed
Sep 04 08:49:48 tux systemd[1]: Started Network Configuration.
Sep 04 08:49:49 tux systemd-networkd[957]: eth0: Interface name change detected, renamed to enp6s0.
Sep 04 08:49:49 tux systemd-networkd[957]: eth1: Interface name change detected, renamed to enp7s0.

after manually restart (systemctl restart systemd-networkd):

● systemd-networkd.service - Network Configuration
     Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2021-09-04 08:51:47 CEST; 13s ago TriggeredBy: ● systemd-networkd.socket
       Docs: man:systemd-networkd.service(8)
   Main PID: 1167 (systemd-network)
     Status: "Processing requests..."
      Tasks: 1 (limit: 19136)
     Memory: 1.0M
     CGroup: /system.slice/systemd-networkd.service
             └─1167 /lib/systemd/systemd-networkd

Sep 04 08:51:47 tux systemd[1]: Starting Network Configuration...
Sep 04 08:51:47 tux systemd-networkd[1167]: enp6s0: Link UP
Sep 04 08:51:47 tux systemd-networkd[1167]: enp6s0: Gained carrier
Sep 04 08:51:47 tux systemd-networkd[1167]: lo: Link UP
Sep 04 08:51:47 tux systemd-networkd[1167]: lo: Gained carrier
Sep 04 08:51:47 tux systemd-networkd[1167]: Enumeration completed
Sep 04 08:51:47 tux systemd[1]: Started Network Configuration.
Sep 04 08:51:48 tux systemd-networkd[1167]: enp6s0: Gained IPv6LL

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From cal@21:1/5 to Tamer Higazi on Sun Sep 5 18:40:02 2021

On 9/5/21 12:46 AM, Tamer Higazi wrote:

Hi people,

After upgrading my gentoo box i see a new behavior, that my machine
after boot doen't configure my network. My network is configured through systemd-network,

Only if I manually after login execute: "systemctl restart
systemd-network" it gets configured.
Can somebody tell me why this is the case and how to fix it ?

systemctl Logs:

after start:

● systemd-networkd.service - Network Configuration
     Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2021-09-04 08:49:48 CEST; 1min
4s 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 04 08:49:48 tux systemd[1]: Starting Network Configuration...
Sep 04 08:49:48 tux systemd-networkd[957]: lo: Link UP
Sep 04 08:49:48 tux systemd-networkd[957]: lo: Gained carrier
Sep 04 08:49:48 tux systemd-networkd[957]: Enumeration completed
Sep 04 08:49:48 tux systemd[1]: Started Network Configuration.
Sep 04 08:49:49 tux systemd-networkd[957]: eth0: Interface name change detected, renamed to enp6s0.
Sep 04 08:49:49 tux systemd-networkd[957]: eth1: Interface name change detected, renamed to enp7s0.

after manually restart (systemctl restart systemd-networkd):

● systemd-networkd.service - Network Configuration
     Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2021-09-04 08:51:47 CEST; 13s ago TriggeredBy: ● systemd-networkd.socket
       Docs: man:systemd-networkd.service(8)
   Main PID: 1167 (systemd-network)
     Status: "Processing requests..."
      Tasks: 1 (limit: 19136)
     Memory: 1.0M
     CGroup: /system.slice/systemd-networkd.service              └─1167 /lib/systemd/systemd-networkd

Sep 04 08:51:47 tux systemd[1]: Starting Network Configuration...
Sep 04 08:51:47 tux systemd-networkd[1167]: enp6s0: Link UP
Sep 04 08:51:47 tux systemd-networkd[1167]: enp6s0: Gained carrier
Sep 04 08:51:47 tux systemd-networkd[1167]: lo: Link UP
Sep 04 08:51:47 tux systemd-networkd[1167]: lo: Gained carrier
Sep 04 08:51:47 tux systemd-networkd[1167]: Enumeration completed
Sep 04 08:51:47 tux systemd[1]: Started Network Configuration.
Sep 04 08:51:48 tux systemd-networkd[1167]: enp6s0: Gained IPv6LL

What does your networkd configuration look like? One thing that stands
out from your example logs is that the first networkd startup seems to
occur _before_ udev assigns predictable network interface names (eth0 -> enp6s0), I'm wondering if that's why it works after you later restart
the daemon.

I'm not a systemd expert -- perhaps there is a dependency ordering issue
here? https://github.com/systemd/systemd/issues/7293

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw@21:1/5 to th982a@googlemail.com on Sun Sep 5 19:10:02 2021

On Sun, Sep 5, 2021 at 2:46 AM Tamer Higazi <th982a@googlemail.com> wrote:

Hi people,

After upgrading my gentoo box i see a new behavior, that my machine
after boot doen't configure my network. My network is configured through systemd-network,

Only if I manually after login execute: "systemctl restart
systemd-network" it gets configured.
Can somebody tell me why this is the case and how to fix it ?

Could you please tell us the output of:

systemctl status systemd-networkd.socket
systemd-networkd-wait-online.service

*before* you restart 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

<div dir="ltr"><div dir="ltr">On Sun, Sep 5, 2021 at 2:46 AM Tamer Higazi <<a href="mailto:th982a@googlemail.com">th982a@googlemail.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;
border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi people,<br>

After upgrading my gentoo box i see a new behavior, that my machine <br>
after boot doen't configure my network. My network is configured through <br>
systemd-network,<br>

Only if I manually after login execute: "systemctl restart <br> systemd-network" it gets configured.<br>
Can somebody tell me why this is the case and how to fix it ?<br></blockquote><div><br></div><div>Could you please tell us the output of:</div><div><br></div><div>systemctl status systemd-networkd.socket systemd-networkd-wait-on

From Tamer Higazi@21:1/5 to All on Sun Sep 5 20:40:02 2021

Dear Dr. Valdés,

As requested the desired output.

tux / # systemctl status systemd-networkd.socket systemd-networkd-wait-online.service
● systemd-networkd.socket - Network Service Netlink Socket
     Loaded: loaded (/lib/systemd/system/systemd-networkd.socket;
enabled; vendor preset: disabled)
     Active: active (running) since Sun 2021-09-05 20:20:18 CEST; 13min ago
   Triggers: ● systemd-networkd.service
       Docs: man:systemd-networkd.service(8)
             man:rtnetlink(7)
     Listen: route 1361 (Netlink)
     CGroup: /system.slice/systemd-networkd.socket

Notice: journal has been rotated since unit was started, output may be incomplete.

× systemd-networkd-wait-online.service - Wait for Network to be Configured
     Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled;
vendor preset: disabled)
     Active: failed (Result: exit-code) since Sun 2021-09-05 20:22:19 CEST; 11min ago
       Docs: man:systemd-networkd-wait-online.service(8)
   Main PID: 984 (code=exited, status=1/FAILURE)

Sep 05 20:20:18 tux systemd[1]: Starting Wait for Network to be
Configured...
Sep 05 20:22:19 tux systemd-networkd-wait-online[984]: Timeout occurred
while waiting for network connectivity.
Sep 05 20:22:19 tux systemd[1]: systemd-networkd-wait-online.service:
Main process exited, code=exited, status=1/FAILURE
Sep 05 20:22:19 tux systemd[1]: systemd-networkd-wait-online.service:
Failed with result 'exit-code'.
Sep 05 20:22:19 tux systemd[1]: Failed to start Wait for Network to be Configured.

Am 9/5/21 um 7:07 PM schrieb Canek Peláez Valdés:

On Sun, Sep 5, 2021 at 2:46 AM Tamer Higazi <th982a@googlemail.com <mailto:th982a@googlemail.com>> wrote:

Hi people,

After upgrading my gentoo box i see a new behavior, that my machine
after boot doen't configure my network. My network is configured
through
systemd-network,

Only if I manually after login execute: "systemctl restart
systemd-network" it gets configured.
Can somebody tell me why this is the case and how to fix it ?

Could you please tell us the output of:

systemctl status systemd-networkd.socket
systemd-networkd-wait-online.service

*before* you restart 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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw@21:1/5 to th982a@googlemail.com on Sun Sep 5 22:00:02 2021

On Sun, Sep 5, 2021 at 1:36 PM Tamer Higazi <th982a@googlemail.com> wrote: [...]

× systemd-networkd-wait-online.service - Wait for Network to be Configured
Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled;
vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2021-09-05 20:22:19
CEST; 11min ago
Docs: man:systemd-networkd-wait-online.service(8)
Main PID: 984 (code=exited, status=1/FAILURE)

Sep 05 20:20:18 tux systemd[1]: Starting Wait for Network to be
Configured...
Sep 05 20:22:19 tux systemd-networkd-wait-online[984]: Timeout occurred
while waiting for network connectivity.
Sep 05 20:22:19 tux systemd[1]: systemd-networkd-wait-online.service:
Main process exited, code=exited, status=1/FAILURE
Sep 05 20:22:19 tux systemd[1]: systemd-networkd-wait-online.service:
Failed with result 'exit-code'.
Sep 05 20:22:19 tux systemd[1]: Failed to start Wait for Network to be Configured.

There's your problem: systemd-networkd-wait-online.service is timing out:

Sep 05 20:22:19 tux systemd-networkd-wait-online[984]: Timeout
occurred while waiting for network connectivity.

The systemd-networkd-wait-online service runs relatively early and waits
for *ALL* interfaces it is aware of to be fully configured or failed[1], so
it probably one of your interfaces is taking too long to be ready. Between timing out and you restarting systemd-networkd.service, the interface
reaches the ready state (or fails), and
systemd-networkd-wait-online.service doesn't time out anymore.

By your logs, you have two ethernet interfaces: enp6s0 and enp7s0, the
latter not in use. Do you .network files in /etc/systemd/network/ or /run/systemd/network/? Any changes (uncommented lines) in /etc/systemd/networkd.conf?

Regards.

[1]
https://man7.org/linux/man-pages/man8/systemd-networkd-wait-online.8.html
--
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

<div dir="ltr"><div dir="ltr">On Sun, Sep 5, 2021 at 1:36 PM Tamer Higazi <<a href="mailto:th982a@googlemail.com">th982a@googlemail.com</a>> wrote:<br></div><div>[...]</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
× systemd-networkd-wait-online.service - Wait for Network to be Configured<br>       Loaded: loaded <br> (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; <br>
vendor preset: disabled)<br>
      Active: failed (Result: exit-code) since Sun 2021-09-05 20:22:19 <br>
CEST; 11min ago<br>
        Docs: man:systemd-networkd-wait-online.service(8)<br>
    Main PID: 984 (code=exited, status=1/FAILURE) </blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1

From Tamer Higazi@21:1/5 to All on Mon Sep 6 21:50:02 2021

Dear Dr. Valdés,

/etc/systemd/network/20-wirded.network:

[Match]
Name=enp6s0

[Network]
Address=192.168.0.50/24
Gateway=192.168.0.1

DNS=192.168.0.1

for enp7s0 there is no other network file.

/etc/systemd/networkd.conf:

[Network]
#SpeedMeter=no
#SpeedMeterIntervalSec=10sec
#ManageForeignRoutingPolicyRules=yes
#ManageForeignRoutes=yes
#RouteTable=

[DHCPv4]
#DUIDType=vendor
#DUIDRawData=

[DHCPv6]
#DUIDType=vendor
#DUIDRawData=

remained untouched.

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.

The problem is, how to solve it ....

Because when I don't do anything by hand, nothing occurs.
I believe that the configuration is done before everything is full
available.
(devices created and renamed ....)

I think I found the solution to my problem, but don't know how to
implement it.
systemd-udev-settle.service

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

Any further ideas I am thankful.

best, Tamer Higazi

references: https://github.com/systemd/systemd/issues/7293

Am 9/5/21 um 9:51 PM schrieb Canek Peláez Valdés:

On Sun, Sep 5, 2021 at 1:36 PM Tamer Higazi <th982a@googlemail.com <mailto:th982a@googlemail.com>> wrote:
[...]

× systemd-networkd-wait-online.service - Wait for Network to be
Configured
      Loaded: loaded
(/lib/systemd/system/systemd-networkd-wait-online.service; enabled;
vendor preset: disabled)
      Active: failed (Result: exit-code) since Sun 2021-09-05
20:22:19
CEST; 11min ago
        Docs: man:systemd-networkd-wait-online.service(8)
    Main PID: 984 (code=exited, status=1/FAILURE)

Sep 05 20:20:18 tux systemd[1]: Starting Wait for Network to be
Configured...
Sep 05 20:22:19 tux systemd-networkd-wait-online[984]: Timeout
occurred
while waiting for network connectivity.
Sep 05 20:22:19 tux systemd[1]: systemd-networkd-wait-online.service:
Main process exited, code=exited, status=1/FAILURE
Sep 05 20:22:19 tux systemd[1]: systemd-networkd-wait-online.service:
Failed with result 'exit-code'.
Sep 05 20:22:19 tux systemd[1]: Failed to start Wait for Network
to be
Configured.

There's your problem: systemd-networkd-wait-online.service is timing out:

Sep 05 20:22:19 tux systemd-networkd-wait-online[984]: Timeout occurred while waiting for network connectivity.

The systemd-networkd-wait-online service runs relatively early and
waits for *ALL* interfaces it is aware of to be fully configured or failed[1], so it probably one of your interfaces is taking too long to
be ready. Between timing out and you restarting
systemd-networkd.service, the interface reaches the ready state (or
fails), and systemd-networkd-wait-online.service doesn't time out anymore.

By your logs, you have two ethernet interfaces: enp6s0 and enp7s0, the latter not in use. Do you .network files in /etc/systemd/network/ or /run/systemd/network/? Any changes (uncommented lines) in /etc/systemd/networkd.conf?

Regards.

[1]
https://man7.org/linux/man-pages/man8/systemd-networkd-wait-online.8.html <https://man7.org/linux/man-pages/man8/systemd-networkd-wait-online.8.html> --
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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From antlists@21:1/5 to Tamer Higazi on Mon Sep 6 23:10:01 2021

On 06/09/2021 20:45, Tamer Higazi wrote:

Dear Dr. Valdés,

/etc/systemd/network/20-wirded.network:

^

Typo? Unimportant? Significant?

Cheers,
Wol

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw@21:1/5 to th982a@googlemail.com on Tue Sep 7 04:20:01 2021

On Mon, Sep 6, 2021 at 2:46 PM Tamer Higazi <th982a@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

<div dir="ltr"><div dir="ltr">On Mon, Sep 6, 2021 at 2:46 PM Tamer Higazi <<a href="mailto:th982a@googlemail.com">th982a@googlemail.com</a>> wrote:</div><div dir="ltr">[...]<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
/etc/systemd/network/20-wirded.network:</blockquote><div>[...]</div><div><br></div><div>That looks fine to me.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
for enp7s0 there is no other network file.<br></blockquote><div><br></div><div>That is as it should be.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I think with THIS syste

From =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw@21:1/5 to antlists@youngman.org.uk on Tue Sep 7 04:20:01 2021

On Mon, Sep 6, 2021 at 4:01 PM antlists <antlists@youngman.org.uk> wrote:
[...]

/etc/systemd/network/20-wirded.network:

^

Typo? Unimportant? Significant?

The filename is only used to lexicographically sort the .network files; it doesn't make a difference.

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

<div dir="ltr"><div dir="ltr">On Mon, Sep 6, 2021 at 4:01 PM antlists <<a href="mailto:antlists@youngman.org.uk">antlists@youngman.org.uk</a>> wrote:</div><div dir="ltr">[...]</div><div class="gmail_quote"><blockquote class="gmail_quote" style="
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> /etc/systemd/network/20-wirded.network:<br>
^<br>

Typo? Unimportant? Significant?<br></blockquote><div><br></div><div>The filename is only used to lexicographically sort the .network files; it doesn't make a difference.</div><div><br></div><div>Regards.</div></div>-- <br><div dir="ltr" class="gmail_
signature"><div dir="ltr"><div><div dir="ltr"><div><font face="arial, helvetica, sans-serif">Dr. Canek Peláez Valdés<br>Profesor de Carrera Asociado C<br>Depart

From Tamer Higazi@21:1/5 to All on Tue Sep 7 20:10:01 2021

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 <th982a@googlemail.com <mailto:th982a@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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw@21:1/5 to th982a@googlemail.com on Tue Sep 7 20:50:01 2021

On Tue, Sep 7, 2021 at 1:03 PM Tamer Higazi <th982a@googlemail.com> wrote:

Dear Dr. Valdés,
I am sorry to tell you that the result still remains the same.

That is weird.

I am also not a systemd expert....

but somebody in the mailing list told me, that the "order" of process
might not be right ?

I'm not an expert either, but I use systemd in all my desktops, laptops and servers (3 desktops, 2 laptops and several servers). I have never had any trouble with systemd-networkd.service.

Drop-In: /etc/systemd/system/systemd-networkd.service.d

└─override.conf

I hadn't seen that. What's included in the override?

cat /etc/systemd/system/systemd-networkd.service.d/override.conf

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

<div dir="ltr"><div dir="ltr">On Tue, Sep 7, 2021 at 1:03 PM Tamer Higazi <<a href="mailto:th982a@googlemail.com">th982a@googlemail.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;
border-left:1px solid rgb(204,204,204);padding-left:1ex">Dear Dr. Valdés,<br> I am sorry to tell you that the result still remains the same.<br></blockquote><div><br></div><div>That is weird.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I am also not a systemd expert....<br>
but somebody in the mailing list told me, that the "order" of process <br>
might not be right ?<br></blockquote><div><br></div><div>I'm not an expert either, but I use systemd in all my desktops, laptops and servers (

From =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw@21:1/5 to th982a@googlemail.com on Tue Sep 7 22:10:01 2021

On Tue, Sep 7, 2021 at 2:35 PM Tamer Higazi <th982a@googlemail.com> wrote:

[Unit]
After=systemd-udev-settle.service

I think that's the problem; in my machines, that service is never run. When
did you add the override? What happens if you delete it? (Also remove the [Link] section in your .network file).

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

<div dir="ltr"><div dir="ltr"></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 7, 2021 at 2:35 PM Tamer Higazi <<a href="mailto:th982a@googlemail.com">th982a@googlemail.com</a>> wrote:<br></div><blockquote class="gmail_
quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
[Unit]<br> After=systemd-udev-settle.service<br></blockquote><div><br></div><div>I think that's the problem; in my machines, that service is never run. When did you add the override? What happens if you delete it? (Also remove the [Link] section in your .
network file).</div><div><br></div><div>Regards.</div></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><font face="arial, helvetica, sans-serif">Dr. Canek Peláez Valdés<br>Profesor de Carrera Asociad

From Tamer Higazi@21:1/5 to All on Tue Sep 7 21:40:01 2021

[Unit]
After=systemd-udev-settle.service

Am 9/7/21 um 8:45 PM schrieb Canek Peláez Valdés:

cat /etc/systemd/system/systemd-networkd.service.d/override.conf

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Tamer Higazi@21:1/5 to All on Tue Sep 7 22:30:01 2021

I added the override because of that problem.
I removed the override:

tux /home/tamer # systemctl revert systemd-networkd
Removed /etc/systemd/system/systemd-networkd.service.d/override.conf.
Removed /etc/systemd/system/systemd-networkd.service.d.
tux /home/tamer #

tux /home/tamer # systemctl status systemd-networkd

● systemd-networkd.service - Network Configuration
     Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2021-09-07 22:15:19 CEST; 23s ago TriggeredBy: ● systemd-networkd.socket
       Docs: man:systemd-networkd.service(8)
   Main PID: 958 (systemd-network)
     Status: "Processing requests..."
      Tasks: 1 (limit: 19136)
     Memory: 2.3M
     CGroup: /system.slice/systemd-networkd.service
             └─958 /lib/systemd/systemd-networkd

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.

... and I removed the link.

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

What about yours ?

best, Tamer

Am 9/7/21 um 10:06 PM schrieb Canek Peláez Valdés:

On Tue, Sep 7, 2021 at 2:35 PM Tamer Higazi <th982a@googlemail.com <mailto:th982a@googlemail.com>> wrote:

[Unit]
After=systemd-udev-settle.service

I think that's the problem; in my machines, that service is never run.
When did you add the override? What happens if you delete it? (Also
remove the [Link] section in your .network file).

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw@21:1/5 to th982a@googlemail.com on Wed Sep 8 01:00:02 2021

On Tue, Sep 7, 2021 at 3:21 PM Tamer Higazi <th982a@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

<div dir="ltr"><div dir="ltr">On Tue, Sep 7, 2021 at 3:21 PM Tamer Higazi <<a href="mailto:th982a@googlemail.com">th982a@googlemail.com</a>> wrote:<br></div><div dir="ltr">[...]</div><div class="gmail_quote"><blockquote class="gmail_quote" style="
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Sep 07 22:15:19 tux systemd[1]: Starting Network Configuration...<br>
Sep 07 22:15:19 tux systemd-networkd[958]: lo: Link UP<br>
Sep 07 22:15:19 tux systemd-networkd[958]: lo: Gained carrier<br>
Sep 07 22:15:19 tux systemd-networkd[958]: Enumeration completed<br>
Sep 07 22:15:19 tux systemd[1]: Started Network Configuration.<br>
Sep 07 22:15:20 tux systemd-networkd[958]: eth0: Interface name change <br> detected, renamed to enp6s0.<br>
Sep 07 22:15:20 tux systemd-networkd[958]: eth1: Interface name change <br>
de

From Tamer Higazi@21:1/5 to All on Wed Sep 8 16:20:02 2021

Hi ...

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

Mine is:

tamer@tux ~ $ find /etc/systemd/system -name "systemd-*" -type l /etc/systemd/system/sockets.target.wants/systemd-networkd.socket /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service /etc/systemd/system/network-online.target.wants/systemd-networkd-wait-online.service
/etc/systemd/system/multi-user.target.wants/systemd-networkd.service

I think the problem is somewhere deeper ....

I wish I knew what it might be.

best, Tamer

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw@21:1/5 to th982a@googlemail.com on Wed Sep 8 22:00:02 2021

On Wed, Sep 8, 2021 at 9:14 AM Tamer Higazi <th982a@googlemail.com> wrote: [...]

I think the problem is somewhere deeper ....

I wish I knew what it might be.

Yeah, I don't understand it either. Have you tried using the other network card? With the corresponding change in the .network file, of course.

Just to test.

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

<div dir="ltr"><div dir="ltr">On Wed, Sep 8, 2021 at 9:14 AM Tamer Higazi <<a href="mailto:th982a@googlemail.com">th982a@googlemail.com</a>> wrote:<br></div><div dir="ltr">[...]</div><div class="gmail_quote"><blockquote class="gmail_quote" style="
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I think the problem is somewhere deeper ....<br>

I wish I knew what it might be.<br></blockquote><div><br></div><div>Yeah, I don't understand it either. Have you tried using the other network card? With the corresponding change in the .network file, of course.</div><div><br></div><div>Just to test.<
/div><div> </div><div>Regards.</div></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><font face="arial, helvetica, sans-serif">Dr. Canek Peláez Valdés<br>Profesor de

Who's Online
Recent Visitors
- Bob Worm
  Thu Apr 25 22:17:10 2024
  from Wales, Uk via Telnet
- Keyop
  Thu Apr 25 21:14:50 2024
  from Huddersfield, West Yorkshire via SSH
- Bob Worm
  Fri Apr 26 08:24:20 2024
  from Wales, Uk via Telnet
- Bob Worm
  Fri Apr 26 06:40:30 2024
  from Wales, Uk via Telnet

System Info

Sysop:	Keyop
Location:	Huddersfield, West Yorkshire, UK
Users:	296
Nodes:	16 (2 / 14)
Uptime:	70:23:21
Calls:	6,656
Calls today:	2
Files:	12,200
Messages:	5,332,151
Posted today:	1

[gentoo-user] network do not come up after booting, only manual reloadi

Who's Online

Recent Visitors

System Info