Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Predictable Network Interface Names missing in /etc/network/interfaces of target system #126

Closed
jkirk opened this issue Mar 2, 2019 · 0 comments · Fixed by #127
Closed

Predictable Network Interface Names missing in /etc/network/interfaces of target system #126

jkirk opened this issue Mar 2, 2019 · 0 comments · Fixed by #127

Comments

@jkirk
Copy link
Contributor

jkirk commented Mar 2, 2019 •
edited

grml-debootstrap by default copies /etc/network/interfaces from the host to the target system.

Debian/stretch uses Predictable Network Interface Names by default whereas the current Grml release (currently 2018.12) still uses the traditional/legacy interface name (eth0).
When deploying a Debian/stretch system out of the latest Grml release (currently 2018.12) we have the situation that the /etc/network/interfaces file from the host is copied to the target system which then will boot with no network connection because no Predictable Network Interface Names are configured in it.

When using the option --defaultinterfaces the problem stays the same as only lo and eth0 are configured automatically.

The easiest fix/workaround would be to add a DHCP configuration for all detected Predictable Network Interface Names when using the --defaultinterfaces option. That said, I am not sure how the --vmfile and --vm option should behave. Obviously lo and eth0 are not enough for a Debian/stretch system even in a Virtual Machine, so I think having all detected Predictable Network Interface Names configured as DHCP should do no harm.

Apart from that we should discuss if deploying the host /etc/network/interfaces file by default is (still) the best approach. I would vote for a new option like --hostinterfaces which does that and go for --defaultinterfaces as the new default option.

And while at it, I think Grml should switch to Predictable Network Interface Names by default. I will create an issue for that.
jkirk added a commit to jkirk/grml-debootstrap that referenced this issue Mar 2, 2019
@jkirk
Add DHCP setting for Predictable Network Interface Names
24d9978 
Predictable Network Interface Names were missing the default
/etc/network/interfaces file when using the --defaultinterfaces option.

Added a Networking-Section in the man page to clarify how the network is
configured in the target system and fixed the documentation for the
options --vmfile and --vm. Both options automatically enable the
--defaultinterface option and not the --nointerfaces option.

Closes: grml#126
@jkirk jkirk mentioned this issue Mar 2, 2019
Merged
jkirk added a commit to jkirk/grml-debootstrap that referenced this issue Mar 2, 2019
@jkirk
Add DHCP setting for Predictable Network Interface Names
9a8bfee 
Predictable Network Interface Names were missing the default
/etc/network/interfaces file when using the --defaultinterfaces option.

Added a Networking-Section in the man page to clarify how the network is
configured in the target system and fixed the documentation for the
options --vmfile and --vm. Both options automatically enable the
--defaultinterface option and not the --nointerfaces option.

Closes: grml#126
@mika mika closed this as completed in #127 Mar 2, 2019
@jkirk jkirk mentioned this issue Mar 2, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add DHCP setting for Predictable Network Interface Names jkirk/grml-debootstrap
1 participant
@jkirk