Moved next-server option from global config to subnet config. #93
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
|
This makes sense to me, and it's how I've been running DHCP here at the house for about half a year. I have a multi-nic server that serves as a router, it's connected to two different networks. I don't want my next-server leaking onto the outside network due to it being a global config. Also, moving it into the subnet greatly simplifies the fogDHCP plugin I'm working on. In this plugin, I only want to enable users to easily manipulate subnet listings, not global configs. Moving the next-server into the subnet listing simplifies this. |
mastacontrola
added a commit
that referenced
this pull request
Mar 20, 2016
Moved next-server option from global config to subnet config.
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.
No description provided.