Hello,

I have "learned" the NetworkManager is the default tool for managing networks in FCOS.

This allows me to configure network with CLI.
sudo nmcli conn modify <conn-id> <option>
This configuration is persistent.

However I'm not sure if this is the recommended approach.
Should I use a QEMU/KVM startup parameter
-fw_cfg name=opt/com.coreos/config,file=<path/to/ignition.file>
instead?

What's pro/con using ignition file for FCOS running in KVM?

THX
Thomas

Am 22.01.2020 um 17:47 schrieb Jonathan Lebon:

Hi Thomas,

Network configuration on FCOS is done via Ignition by dropping
NetworkManager keyfiles:
https://developer.gnome.org/NetworkManager/stable/nm-settings-keyfile.html

We need to improve documentation in that area. I filed:
https://github.com/coreos/fedora-coreos-tracker/issues/351

Though the links there point to the canonical references. Searching
the web for keyfile examples should also help. E.g. to tell to leave a
device alone completely, you can drop a keyfile like this at
/etc/NetworkManager/conf.d/ (untested):

[keyfile]
# using interface name
unmanaged-devices=interface-name:<device-name>
# or MAC address
unmanaged-devices=mac:<mac-addr>


On Wed, Jan 22, 2020 at 10:39 AM Thomas Schneider <74cmonty@gmail.com> wrote:

Hi,
I have successfully installed FCOS in KVM from ISO.

Now I added another NIC to the VM, and after rebooting DHCP assigns an IP to this new NIC:
[core@vm191-fcos ~]$ nmcli device
DEVICE  TYPE      STATE            CONNECTION
eth0    ethernet  verbunden        Wired connection 1
eth1    ethernet  verbunden        Wired connection 2
lo      loopback  nicht verwaltet  --
[core@vm191-fcos ~]$ nmcli device show eth1
GENERAL.DEVICE:                         eth1
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         BE:05:3F:16:2C:CD
GENERAL.MTU:                            1500
GENERAL.STATE:                          100 (verbunden)
GENERAL.CONNECTION:                     Wired connection 2
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/2
WIRED-PROPERTIES.CARRIER:               an
IP4.ADDRESS[1]:                         192.168.100.102/24
IP4.GATEWAY:                            192.168.100.11
IP4.ROUTE[1]:                           dst = 0.0.0.0/0, nh = 192.168.100.11, mt = 101
IP4.ROUTE[2]:                           dst = 192.168.100.0/24, nh = 0.0.0.0, mt = 101
IP4.DNS[1]:                             10.17.200.80
IP4.DNS[2]:                             10.17.122.10
IP4.DOMAIN[1]:
IP6.ADDRESS[1]:                         fe80::50f7:c9cd:ec1e:e75/64
IP6.GATEWAY:                            --
IP6.ROUTE[1]:                           dst = fe80::/64, nh = ::, mt = 101
IP6.ROUTE[2]:                           dst = ff00::/8, nh = ::, mt = 256, table=255

However I don't want NetworkManager to control this NIC eth1.
This should be a static IP.

Can you please advise how to disable NetworkManager to control this NIC?

THX
_______________________________________________
CoreOS mailing list -- coreos@lists.fedoraproject.org
To unsubscribe send an email to coreos-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org