tree 7b0df3c63dfc7e1bc6be5e6f36fa183e812699cf
parent a0026d1589e91059b01d87a90b5a3dc0c8b88f4d
author Robert Lubos <robert.lubos@nordicsemi.no> 1675683191 +0100
committer Carles Cufí <carles.cufi@nordicsemi.no> 1675852002 +0100

net: config: Unify the init behaviour when timeout is enabled and not

Currently, if timeout is not configured for the network initialization in
the config module, the initialization function will configure IPv4/IPv6/
DHCPv4 regardless of the interface status. This is not the case when the
timeout is set, and the interface was not brought up during the timeout
period. This lead to ambiguity in terms of interface initialization.

This commits unifies the behaviour between these two cases. The
aforementioned initializations will always take place, regardless of the
interface status. The IPv4/IPv6 and DHCPv4 routines should be prepared
to deal with interfaces that are not brought up. The only difference
now, between timeout and no timeout scenario, is that the former will
report an error in case the timeout occurs wile waiting for the expected
events.

Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>