Avoid VPN and DHCP address space collision #52
Merged
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.
The address spaces for DHCP (10.10.10.50 – 10.10.10.254) and VPN (10.10.10.10 – 10.10.10.59) overlap from 10.10.10.50-10.10.10.59. Fairly sure these are supposed to be distinct spaces. There are two obvious ways to eliminate the overlap.
or
VPN 10.10.10.10.59 --> 10.10.10.49.
I have, rather arbitrarily, chosen the latter.