Fix network initialization during system boot - #4394
Open
everyx wants to merge 2 commits into
Open
Conversation
During Linux system boot, the network stack may not be fully initialized when sing-box starts. The original code would trigger NetworkPause() for a missing default interface, preventing automatic recovery after network initialization completes. Skipping the pause when not yet started lets the router recover once the network has been initialized.
started is written during Start(PostStart) and read without synchronization by netif callbacks running on separate goroutines. Use atomic.Bool to avoid a data race.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fix network initialization during system boot and make the
startedflag atomic to avoid a data race with interface monitor callbacks.