Closed pbronneberg closed 1 month ago
Apparently, I missed an important bit in the documentation of nmc
. Given that it is based on nmstate
, it already supports advanced settings.
@pbronneberg as you mention nmc supports the https://nmstate.io/ API (other than the constraint that mac-address
must be specified to match the configuration with the target host, except when using a unified configuration)
If there are specific gaps perhaps we can raise an upstream nmstate issue, otherwise can this issue now be closed?
@hardys Indeed, Using nmstate solved it.
These are the steps I followed, to generate nmstate from my existing .nmconnection
files.
nmstatectl show -r -s > _all.yaml
Edge image builder nicely picked up the configuration, and after first boot my system had the desired network settings.
Issue can be closed!
Situation
At the moment, Edge Image Builder supports configuring network connections based on the new
nmc
format. This format supports basic settings to e.g. set static IP addresses, but is not yet feature equivalent to.nmconnection
.For our use-case, we e.g. create a bridge interface, set jumbo-frames, and connect our
eth1
interface to the bridge (use-case for the bridge is to connect multiple physical networks to a container usingmultus-cni
)Current work-around
To work around this, we can create a custom combustion script, that copies
.nmconnection
files to a desired location. so that they are picked up at first boot. Given that, in our use-case, the network configuration of the 2nd physical network is identical for each device, we don't need node specific adaptations to our configuration.Request
EIB support for.nmconnection
filesnmc
support for advanced network settings-or- document default location of.nmconnection
files asos-files/etc/NetworkManager/system-connections
Example configuration we want to set