New Hardware, new install: Boot takes long time

[malcolmlewis]

@dcurtisfra

The simple fact is, Wicked is taking about 30 seconds to complete it’s setup – which is way too long for an “IPv4 only” system.

And, as we can see, it ain’t an “IPv4 only” system – there’s IPv6 in there as well.
And, even with IPv6 enabled, 30 seconds is a little bit too long for the IPv6 address resolution

Hi
Which is the default wicked setting for interfaces to come up, change to 1 and all is good…

1.225s wicked.service

Yes, disable and mask the services…

systemctl list-unit-files --state=masked | grep wick

wickedd-auto4.service                        masked disabled
wickedd-dhcp4.service                        masked disabled
wickedd-dhcp6.service                        masked disabled

[dcurtisfra]

@malcolmlewis

Which is the default wicked setting for interfaces to come up, change to 1 and all is good…

AFAIK, in ‘/etc/sysconfig/network/config’ the parameter “WAIT_FOR_INTERFACES” is the time Wicked waits for hot-plugged interfaces to come up.

• Before, it kicks the DHCP queries into life …

For example –

    6.057900] kernel: libphy: r8169: probed
    6.058063] kernel: r8169 0000:03:00.0 eth0: RTL8168h/8111h, d4:5d:64:a5:f5:0e, XID 541, IRQ 70
    6.058064] kernel: r8169 0000:03:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
 .
 .
 .
    7.353828] systemd[1]: Reached target Host and Network Name Lookups.
    7.867157] systemd[1]: Reached target Network (Pre).
    7.868530] systemd[1]: Starting wicked AutoIPv4 supplicant service...
 .
 .
 .
    7.933027] systemd[1]: Starting wicked managed network interfaces...
    9.336055] kernel: Generic FE-GE Realtek PHY r8169-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE)
    9.544417] kernel: r8169 0000:03:00.0 eth0: Link is Down
   12.593718] kernel: r8169 0000:03:00.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx
   12.593735] kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   12.444803] wickedd-dhcp4[1315]: eth0: Request to acquire DHCPv4 lease with UUID 08e93262-f5c9-0300-2f05-000005000000
   12.447197] wickedd-dhcp6[1316]: eth0: Request to acquire DHCPv6 lease with UUID 08e93262-f5c9-0300-2f05-000006000000 in mode auto

Wicked starts after [amongst other things] the Network (pre) target and then waits at most “WAIT_FOR_INTERFACES” seconds before sending DHCP requests – logical – it needs a functioning interface for the requests.

• In this example, Wicked has to wait about 4½ seconds before the Kernel (finally) activates the network interface …
• The “WAIT_FOR_INTERFACES” timer has not expired – it is killed when Kernel brings the interface up …

[malcolmlewis]

@dcurtisfra

AFAIK, in ‘/etc/sysconfig/network/config’ the parameter “WAIT_FOR_INTERFACES” is the time Wicked waits for hot-plugged interfaces to come up.

• Before, it kicks the DHCP queries into life …

For example –

    6.057900] kernel: libphy: r8169: probed
    6.058063] kernel: r8169 0000:03:00.0 eth0: RTL8168h/8111h, d4:5d:64:a5:f5:0e, XID 541, IRQ 70
    6.058064] kernel: r8169 0000:03:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
 .
 .
 .
    7.353828] systemd[1]: Reached target Host and Network Name Lookups.
    7.867157] systemd[1]: Reached target Network (Pre).
    7.868530] systemd[1]: Starting wicked AutoIPv4 supplicant service...
 .
 .
 .
    7.933027] systemd[1]: Starting wicked managed network interfaces...
    9.336055] kernel: Generic FE-GE Realtek PHY r8169-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE)
    9.544417] kernel: r8169 0000:03:00.0 eth0: Link is Down
   12.593718] kernel: r8169 0000:03:00.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx
   12.593735] kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   12.444803] wickedd-dhcp4[1315]: eth0: Request to acquire DHCPv4 lease with UUID 08e93262-f5c9-0300-2f05-000005000000
   12.447197] wickedd-dhcp6[1316]: eth0: Request to acquire DHCPv6 lease with UUID 08e93262-f5c9-0300-2f05-000006000000 in mode auto

Wicked starts after [amongst other things] the Network (pre) target and then waits at most “WAIT_FOR_INTERFACES” seconds before sending DHCP requests – logical – it needs a functioning interface for the requests.

• In this example, Wicked has to wait about 4½ seconds before the Kernel (finally) activates the network interface …
• The “WAIT_FOR_INTERFACES” timer has not expired – it is killed when Kernel brings the interface up …

Hi
I don’t use dhcp, it’s a desktop

[MrNice]

@dcurtisfra

You need to check the link via the aerial on the roof to your ISP –

• That link may be using IPv6 because, that’s the way you ISP possibly/probably wants it.
• You’ll also have to check if, there’s an IPv4 tunnel to your ISP.

Then, you need to check if, your modem/router supports IPv4 only on the LAN/WLAN interfaces given that, your ISP probably/possibly wants to use IPv6 on the interface supporting the link via the wireless aerial on your roof …

Thank you dcurtisfra and thank you malcolmlewis for your contribution about my network setting.

I sent a mail to my ISP about IPv4/IPv6. I am waiting for an answer but it’s Patrick’s day week-end, so everything here is closed. I’ll post again as soon I get the answer.
Please keep an eye on the thread. Thanks