Removing resolvconf Installation from debian and ubuntu installation
#482
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
Anatr0p
pushed a commit
to Anatr0p/wireguard-install
that referenced
this pull request
Nov 11, 2023
- Kali Linux support - Removed resolvconf installation - Automatic PersistentKeepalive - Config file output right after client creation under QR code - Changed y/n to yes/no to avoid accidental press - Added confirmation for client removing - Replaced way to detect machine IPv4/6 - Updated permissions for whole /etc/wireguard from 644 to 600 - Added IPv6 random generation Used issues/PRs: angristan#474 angristan#430 angristan#482 by bushwhackr angristan#457 by dikeckaan angristan#456 by turekt
Repository owner
deleted a comment from
Anatr0p
Nov 13, 2023
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.
Referencing issue: #479
Most cloud providers injects their own DNS settings into /etc/resolv.conf file and/or running a separate DNS provider such as systemd-resolved. Running
apt-get install resolveconfwill break /etc/resolv.conf.Tested with GCP debian-cloud/debian-12 image, both DNS proxying for clients and local DNS lookup still works.