feat: support to bind to lan lazily and re-bind to lan #166
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
Sometimes, we want to bind a
LAN
interface once it is brought up (NewLink).For example, I want to bind dae to
ap0
once I start to share my hotspot. However, I do not exactly know when in the future I will start to share my hotspot and create anap0
. dae will fail to start if fail to bind any LAN interfaces.Another problem is that if my
ap0
is deleted, whenap0
is created in the future,dae
will not bind to it again.This PR fixes it.
Checklist
Full changelogs
link not found
, wait forRTM_NEWLINK
and bind to it.RTM_NEWLINK
and bind to it.