+
+
In general, startup complete is not reached as long as NetworkManager is busy activating a device and as long as there are profiles in activating state. During boot, NetworkManager starts autoactivating @@ -84,7 +85,15 @@ setting). While trying and retrying, NetworkManager is busy until all profiles and devices either reached an activated or disconnected state and no further events are expected. -

+ Basically, as long as there are devices and connections in activating + state visible with nmcli device and nmcli connection, + startup is still pending. +

When a device reaches activated state, depends on its configuration. For example, with a profile with both IPv4 and IPv6 addressing @@ -104,10 +113,24 @@ without ports, NetworkManager-wait-online.service blocks until timeout. This is a configuration error.
+ Dispatcher scripts for the "pre-up" event run at a late stage during activation + of a profile. These scripts block the activation for when NetworkManager considers + the profile fully activated. + See also NetworkManager-dispatcher(8) + for details. +
+ The connection property connection.wait-activation-delay also + adds an additional delay during activation and delays startup complete. This is to + workaround certain cases where a device is known to not be ready for a certain + amount of time. +
The property connection.wait-device-timeout of the connection profiles waits until the waited devices appear. This is useful if the driver - takes a longer time to detect the networking interfaces. + takes a longer time to detect the networking interfaces. Similar with the + connection.gateway-ping-timeout property.
With Wi-Fi devices, NetworkManager needs to wait for the first scan -- cgit 1.3.0-6-gf8a5