Support configuring network locations #1048
Open
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
|
Can you rebase this on master? |
tjni
force-pushed
the
network-locations
branch
2 times, most recently
from
04a1cba to
c7bf74e
Compare
|
Done! |
tjni
force-pushed
the
network-locations
branch
from
c7bf74e to
ebe9356
Compare
Enzime
changed the title
tjni
force-pushed
the
network-locations
branch
3 times, most recently
from
60e32dc to
690601e
Compare
tjni
force-pushed
the
network-locations
branch
4 times, most recently
from
82bec0b to
630c7c6
Compare
tjni
force-pushed
the
network-locations
branch
from
630c7c6 to
a560de3
Compare
tjni
force-pushed
the
network-locations
branch
2 times, most recently
from
a568db3 to
b185b6a
Compare
tjni
force-pushed
the
network-locations
branch
4 times, most recently
from
4e03543 to
27be7a7
Compare
tjni
force-pushed
the
network-locations
branch
from
27be7a7 to
e74d601
Compare
tjni
force-pushed
the
network-locations
branch
3 times, most recently
from
09e73b7 to
9f7bb93
Compare
tjni
force-pushed
the
network-locations
branch
from
9f7bb93 to
5387b21
Compare
tjni
force-pushed
the
network-locations
branch
from
5387b21 to
8104a7c
Compare
|
I would love to see this merged :) Using different DNS arrangements is also my use case. |
tjni
force-pushed
the
network-locations
branch
from
8104a7c to
d7efcbc
Compare
This adds support for configuring DNS servers and search domains for each location. This is exposed through the networking.location option. The networking.knownNetworkServices option now applies globally across all locations. The networking.dns and networking.search options are now aliases under networking.location.Automatic, since the "Automatic" network location is the default location on an unconfigured system.
tjni
force-pushed
the
network-locations
branch
from
d7efcbc to
f55115b
Compare
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.
This adds support for configuring DNS servers and search domains for each location.
This is exposed through the
networking.locationoption. Thenetworking.knownNetworkServicesoption now applies globally across all locations.The
networking.dnsandnetworking.searchoptions are now aliases undernetworking.location.Automatic, since the "Automatic" network location is the default location on an unconfigured system.Below is a sample from my own configuration illustrating usage. I configure DNS servers on my Home location in order to bypass my AT&T router adding AT&T's DNS server automatically: