1NETWORKMANAGER-WAIT-ONLINE(N8e)twork management daemoNnEsTWORKMANAGER-WAIT-ONLINE(8)
2
6 NetworkManager-wait-online.service - Wait for the network to come
7 online
8
10 The NetworkManager-wait-online service is a oneshot systemd service
11 that delays reaching the network-online target until NetworkManager
12 reports that the startup is completed on the D-Bus.
13 When the system boots, for example, remote mounts defined in
15 /etc/fstab, require that the network is up. For this, these systemd
16 units contain the After=network-online.target setting to order
17 themselves after this target. NetworkManager-wait-online ensures that
18 the network-online target is reached only after the network is
19 available.
20 Optimally, all services on the host react dynamically to network
22 changes and systemd services do not need to be configured to start
23 after reaching the network-online target. In this case,
24 NetworkManager-wait-online.service has no effect and does not delay the
25 boot time. On the other hand, if you encounter a long boot time due to
26 the delay of NetworkManager-wait-online, investigate the services that
27 require network access and fix them.
28 Except for the time out value in the NetworkManager-wait-online.service
30 unit, you cannot configure this service. Instead, settings in
31 NetworkManager and the connection profiles affect the behavior:
32 • Startup is not complete as long as NetworkManager profiles are in
34 an activating state. During boot, NetworkManager starts profiles
35 with the connection.autoconnect=yes setting. If activation fails,
36 NetworkManager retries the activation depending on the value of the
37 connection.autoconnect-retries setting.
38 NetworkManager reports startup complete when all profiles and
40 devices are either activated or in a disconnect state and no
41 further events are expected.
42 • When a device reaches the activate state depends on its
44 configuration. For example, with a profile that has both IPv4 and
45 IPv6 enabled, by default, NetworkManager considers the device as
46 fully activated already when only one of the address families is
47 ready.
48 The ipv4.may-fail and ipv6.may-fail settings control this behavior.
50 Additionally, the following settings influence when the two address
51 families complete: ipv4.required-timeout, ipv6.required-timeout,
52 ipv4.dhcp-timeout, and ipv6.ra-timeout. For details, see nm-
53 settings-nmcli(5).
54 • NetworkManager cannot set IP addresses on bridge and bond devices
56 that have ports that do not auto-activate. Because of this
57 configuration error, NetworkManager-wait-online blocks until the
58 service reaches its timeout value.
59 • Dispatcher scripts for the pre-up event run at a late stage during
61 activation of a profile. These scripts block the activation for
62 when NetworkManager considers the profile fully activated. For
63 details, see NetworkManager-dispatcher(8).
64 • The property connection.wait-activation-delay adds an additional
66 delay during activation and delays startup complete. This setting
67 works around certain cases where a device is known to not be ready
68 for a certain amount of time.
69 • The property connection.wait-device-timeout in the connection
71 profiles cause a delay until the waiting devices appear. This is
72 useful if the driver takes a longer time to detect the networking
73 interfaces. This setting is similar to the
74 connection.gateway-ping-timeout property.
75 • With Wi-Fi devices, NetworkManager needs to wait for the first scan
77 result to know which networks are available. That adds a delay.
78 • With Ethernet devices, NetworkManager waits for the carrier until
80 the value in [device*].carrier-wait-timeout is reached. This is
81 because some devices take a long time to detect the carrier.
82 Consequently, booting with cable unplugged, unnecessarily delays
83 NetworkManager-wait-online.service.
84
86 Please report any bugs in NetworkManager at the NetworkManager issue
87 tracker[1].
88
90 NetworkManager home page[2], NetworkManager(8), nm-online(1), the
91 network-online.target description in systemd.special(7)
92
94 1. NetworkManager issue tracker
95 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues
96 2. NetworkManager home page
98 https://networkmanager.dev
99NetworkManager-wait-online NETWORKMANAGER-WAIT-ONLINE(8)