Description of problem: one can specify static_networks in kickstart metadata to have automatically set up specific networks on defined interfaces. I was not able to find a way how to set up a DHCP assignment on these networks. So my proposal is to add dhcp_networks to the network snippet like this: {% if dhcp_networks %} {% for device in dhcp_networks|split(';') %} network --bootproto=dhcp --device={{ device }} {% endfor %} {% endif %} That accepts dhcp_networks="MAC1;MAC2;...;MACn" and sets them up as DHCP interfaces. Version-Release number of selected component (if applicable): 0.11.3
(In reply to comment #0) > network --bootproto=dhcp --device={{ device }} Hmmm, I don't understand why this is necessary. Isn't DHCP the default? What does anaconda do differently if this line is present vs. absent? From my reading of: http://fedoraproject.org/wiki/Anaconda/Kickstart#network it seems like this should make no difference.
They are set up as DHCP, but disabled (ONBOOT=no).
Okay, I see.
On Gerrit: http://gerrit.beaker-project.org/3107
The development version of the docs have been updated to include this ksmeta variable: https://beaker-project.org/docs-develop/user-guide/customizing-installation.html#kickstart-metadata
Beaker 0.17.0 has been released.