-
Notifications
You must be signed in to change notification settings - Fork 114
network: fall back to static configuration #2334
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason we don't want to fall back to 10.0.5.3 if no DHCP configuration is acquired? I feel like that would simplify the logic a bit, and the way I see it, HERMIT_IP is supposed to overwrite the 10.0.5.3 default, having it also imply enabling the fallback is a bit unintuitive. I wouldn't mind always falling back to the static configuration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My impression is that it is not good practice to claim an IP address without explicit input from the user. When DHCP is not enabled, it is reasonable to infer that the user wants a static IP and if one is not provided use the default, but if DHCP is enabled we shouldn't claim an address without the user asking for it.
Always falling back to the default would also mean that the user has no way of preventing the kernel from claiming an address. I guess we could make it so that when HERMIT_IP is set to something like 0.0.0.0 we don't set an address, but I think the behaviour in the PR is safer.
For the suggested change, I personally prefer to stay in the normal Rust land as opposed to the configuration specification language as much as possible, but I also don't really mind the alternative.