Added GUI instructions for connecting to a hidden network #3133
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
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.
Follow-up to Bookworm networking improvements inspired by @lurch's comment in the Bookworm networking PR.
Unfortunately the GUI actually makes this a little more confusing than the CLI -- with the CLI, it's easy enough to just ask users for an SSID and password and assume that if they use some more complicated security scheme they can ask their admin about it or read the man pages. In the GUI, users have to specifically choose their security scheme. So I've opted to give a strong nudge towards WPA2, which is the most likely choice to work for most networks. Something something ask your network administrator if WPA2 enterprise is right for you.