You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 17, 2022. It is now read-only.
When setting a network device up (via netlink) the function returns before the network device is actually in state up.
Assigning routes to a network device (via netlink) requires the network device to be up.
I think the caller should safely assume that .await for the async function init/network.rs:set_link_up assures that the link is up, so that follow up network configuration steps can safely assume that the link is really up after the call.
In addition, I would like to provide access to the netdevice state during network configuration, so that a config functions relying on a link state can implement safety checks.
The text was updated successfully, but these errors were encountered:
When setting a network device up (via netlink) the function returns before the network device is actually in state up.
Assigning routes to a network device (via netlink) requires the network device to be up.
I think the caller should safely assume that
.await
for theasync
functioninit/network.rs:set_link_up
assures that the link is up, so that follow up network configuration steps can safely assume that the link is really up after the call.In addition, I would like to provide access to the netdevice state during network configuration, so that a config functions relying on a link state can implement safety checks.
The text was updated successfully, but these errors were encountered: