-
Notifications
You must be signed in to change notification settings - Fork 759
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simplify inital setup Q&A steps #491
Comments
I like this. I have another idea for simplicity that I want to try before we focus
|
I like this. I have another idea for simplicity that I want to try before we focus
|
|
An user noted that the auto-configuration could show the type of config that it would do before the timer starts. |
|
I tried playing with this, but other than condensing text this doesn't add a benefit at the price of somebody else not having enough information. Personally, I shift through the steps without reading anymore. Closing. |
The questions asked during initial setup (or to change interfaces via the console) are quite verbose and take much time to read and understand. The questions should be short keywords and not complete sentences to avoid misinterpretation or errors of the user.
Example:
Suggestion:
In my opinion even more confusing is the IP address assignment via the console:
Currently:
What confused me the most the first time I've seen that Q&A session was the gateway question
For a WAN, enter the new LAN IPv4 upstream gateway address. For a LAN, press <ENTER> for none:. I was asking myself why am I asked the WAN gateway now? I'm configuring the LAN interface, am I?...Suggestion:
Also the explanations about netmask notations (decimal vs. CIDR) is not really required anymore, especially for IPv6. I've never even seen IPv6 noted netmasks in a different notation than CIDR.
The text was updated successfully, but these errors were encountered: