-
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
automatic interface assignment may not be the best thing in the world #5
Comments
|
Lets make it more clever and have first two interfaces setup as LAN/WAN or if only one setup as WAN. |
fichtner
added a commit
that referenced
this issue
Jul 1, 2015
Boy, this is a fun one! :) Still some work to do, but seems really good for headless installation or just being plain sloppy. Needed do adapt timeout() to return the actual input char, so that we can do the `any key' prompt.
fichtner
added a commit
that referenced
this issue
Jul 1, 2015
fichtner
added a commit
that referenced
this issue
Jul 1, 2015
Always unload LAN if previously set. Otherwise no code changes.
fichtner
added a commit
that referenced
this issue
Jul 1, 2015
fichtner
added a commit
that referenced
this issue
Jul 1, 2015
fichtner
added a commit
that referenced
this issue
Jul 1, 2015
fichtner
added a commit
that referenced
this issue
Jul 2, 2015
Unsetting LAN, later setting it will strip the defaults from the interface section so try to avoid that by always settings defaults.
fichtner
added a commit
that referenced
this issue
Jul 2, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With em0 and em1 present the config currently skips interface assignment. Want to deploy a better way of doing that consistently. Also, initial IP assignment is missing. Workarounds like the LiveCD exist, but are a little too inconvenient on first glance. via @TimelessP (twitter)
The text was updated successfully, but these errors were encountered: