fix(metal/dhcp): use IP lease range based on network CIDR #41
Conversation
This file contains 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
khuedoan
changed the title
zanehala
added a commit
to zanehala/homelab
that referenced
this pull request
Mar 16, 2023
…from renovate/all-minor-patch into master Reviewed-on: https://git.zanelab.com/zhala/homelab/pulls/41
retX0
pushed a commit
to retX0/homelab
that referenced
this pull request
Mar 15, 2024
…from renovate/all-minor-patch into master Reviewed-on: https://git.qos.cc/ops/homelab/pulls/41
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
BUG: sometime, the default gateway ip is not always .1, thus not stable to use as lease ip range for dhcp.
For example: if your default gaateway IP is 192.168.1.253, then your dhcp lease range is 192.168.1.254-192.168.1.254, and the pxe boot process won't work