Re: 'unmanaged' via keyfile plugin - not quite

[poma <pomidorabelisima gmail com>]

On 23.03.2014 15:57, poma wrote:
> ~~~~~~~~~~~~~~~~
> ifcfg-rh plugin:
> ~~~~~~~~ ~~~~~~~
>
> /etc/NetworkManager/NetworkManager.conf:
> [main]
> plugins=ifcfg-rh
>
> /etc/sysconfig/network-scripts/ifcfg-enp3s0:
> ...
> NM_CONTROLLED=no
>
> $ nmcli device status
> DEVICE  TYPE      STATE         CONNECTION
> ...
> enp3s0  ethernet  unmanaged     --
> ...
>
> $ nmcli -f GENERAL.STATE device show enp3s0
> GENERAL.STATE:                          10 (unmanaged)
>
> # journalctl -b -u NetworkManager --no-pager
> ...
> NetworkManager[1462]: <info> NetworkManager (version
> 0.9.9.1-4.git20140319.fc20) is starting...
> NetworkManager[1462]: <info> Read config:
> /etc/NetworkManager/NetworkManager.conf and conf.d: 00-server.conf
> NetworkManager[1462]: ifcfg-rh: Acquired D-Bus service com.redhat.ifcfgrh1
> NetworkManager[1462]: <info> Loaded plugin ifcfg-rh: (c) 2007 - 2013 Red
> Hat, Inc.  To report bugs please use the NetworkManager mailing list.
> NetworkManager[1462]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red
> Hat, Inc.  To report bugs please use the NetworkManager mailing list.
> NetworkManager[1462]: ifcfg-rh: parsing
> /etc/sysconfig/network-scripts/ifcfg-enp3s0 ...
> NetworkManager[1462]: ifcfg-rh:     read connection 'enp3s0'
> NetworkManager[1462]: ifcfg-rh: Ignoring connection 'enp3s0' / device
> '...' due to NM_CONTROLLED=no.
> NetworkManager[1462]: <info> Networking is enabled by state file
> NetworkManager[1462]: <info> (enp3s0): carrier is OFF (but ignored)
> NetworkManager[1462]: <info> (enp3s0): new Ethernet device (driver:
> 'r8169' ifindex: 4)
> NetworkManager[1462]: <info> (enp3s0): exported as
> /org/freedesktop/NetworkManager/Devices/3
> systemd[1]: Started Network Manager.
> NetworkManager[1462]: <info> startup complete
>
>                           -- unmanaged OK --
>
> ~~~~~~~~~~~~~~~
> keyfile plugin:
> ~~~~~~~ ~~~~~~~
>
> /etc/NetworkManager/conf.d/custom.conf:
> [main]
> plugins=keyfile
>
> [keyfile]
> unmanaged-devices=interface-name:enp3s0
>
> /etc/NetworkManager/system-connections/enp3s0:
> ...
> [connection]
> id=enp3s0
> ...
>
> $ nmcli device status
> DEVICE  TYPE      STATE         CONNECTION
> enp3s0  ethernet  connected     enp3s0
> ...
>
> $ nmcli -f GENERAL.STATE device show enp3s0
> GENERAL.STATE:                          100 (connected)
>
> # journalctl -b -u NetworkManager
> ...
> NetworkManager[1446]: <info> NetworkManager (version
> 0.9.9.1-4.git20140319.fc20) is starting...
> NetworkManager[1446]: <info> Read config:
> /etc/NetworkManager/NetworkManager.conf and conf.d: 00-server.conf,
> custom.conf
> NetworkManager[1446]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red
> Hat, Inc.  To report bugs please use the NetworkManager mailing list.
> NetworkManager[1446]: keyfile: new connection
> /etc/NetworkManager/system-connections/enp3s0
> systemd[1]: Started Network Manager.
> NetworkManager[1446]: <info> Networking is enabled by state file
> NetworkManager[1446]: <info> (enp3s0): carrier is OFF (but ignored)
> NetworkManager[1446]: <info> (enp3s0): new Ethernet device (driver:
> 'r8169' ifindex: 4)
> NetworkManager[1446]: <info> (enp3s0): exported as
> /org/freedesktop/NetworkManager/Devices/3
> NetworkManager[1446]: <info> (enp3s0): device state change: unmanaged ->
> unavailable (reason 'managed') [10 20 2]
> NetworkManager[1446]: <info> (enp3s0): preparing device
> NetworkManager[1446]: <info> (enp3s0): device state change: unavailable
> -> disconnected (reason 'none') [20 30 0]
> NetworkManager[1446]: <info> Auto-activating connection 'enp3s0'.
> NetworkManager[1446]: <info> Activation (enp3s0) starting connection
> 'enp3s0'
> NetworkManager[1446]: <info> Activation (enp3s0) Stage 1 of 5 (Device
> Prepare) scheduled...
> NetworkManager[1446]: <info> Activation (enp3s0) Stage 1 of 5 (Device
> Prepare) started...
> NetworkManager[1446]: <info> (enp3s0): device state change: disconnected
> -> prepare (reason 'none') [30 40 0]
> NetworkManager[1446]: <info> NetworkManager state is now CONNECTING
> NetworkManager[1446]: <info> Activation (enp3s0) Stage 2 of 5 (Device
> Configure) scheduled...
> NetworkManager[1446]: <info> Activation (enp3s0) Stage 1 of 5 (Device
> Prepare) complete.
> NetworkManager[1446]: <info> Activation (enp3s0) Stage 2 of 5 (Device
> Configure) starting...
> NetworkManager[1446]: <info> (enp3s0): device state change: prepare ->
> config (reason 'none') [40 50 0]
> NetworkManager[1446]: <info> Activation (enp3s0) Stage 2 of 5 (Device
> Configure) successful.
> NetworkManager[1446]: <info> Activation (enp3s0) Stage 2 of 5 (Device
> Configure) complete.
> NetworkManager[1446]: <info> (enp3s0): link connected
> NetworkManager[1446]: <info> Activation (enp3s0) Stage 3 of 5 (IP
> Configure Start) scheduled.
> NetworkManager[1446]: <info> Activation (enp3s0) Stage 3 of 5 (IP
> Configure Start) started...
> NetworkManager[1446]: <info> (enp3s0): device state change: config ->
> ip-config (reason 'none') [50 70 0]
> NetworkManager[1446]: <info> Activation (enp3s0) Stage 5 of 5 (IPv4
> Configure Commit) scheduled...
> NetworkManager[1446]: <info> Activation (enp3s0) Stage 3 of 5 (IP
> Configure Start) complete.
> NetworkManager[1446]: <info> Activation (enp3s0) Stage 5 of 5 (IPv4
> Commit) started...
> NetworkManager[1446]: <info> (enp3s0): device state change: ip-config ->
> ip-check (reason 'none') [70 80 0]
> NetworkManager[1446]: <info> Activation (enp3s0) Stage 5 of 5 (IPv4
> Commit) complete.
> NetworkManager[1446]: <info> (enp3s0): device state change: ip-check ->
> secondaries (reason 'none') [80 90 0]
> NetworkManager[1446]: <info> (enp3s0): device state change: secondaries
> -> activated (reason 'none') [90 100 0]
> NetworkManager[1446]: <info> NetworkManager state is now CONNECTED_LOCAL
> NetworkManager[1446]: <info> Policy set 'enp3s0' (enp3s0) as default for
> IPv4 routing and DNS.
> NetworkManager[1446]: <info> Activation (enp3s0) successful, device
> activated.
> NetworkManager[1446]: <info> startup complete
> NetworkManager[1446]: <info> NetworkManager state is now CONNECTED_GLOBAL
>
>                           -- unmanaged NOPE --

In the end it turns out that even with "unmanaged" via NetworkManager's
'ifcfg-rh' plugin(NM_CONTROLLED=no) the whole thing is broken.
If the systemd-networkd is running side by side with NetworkManager,
trying to drive the "unmanaged" devices, both services collide and the
network is cowabungad. It only works if the one of the services is
offline, no tricks.
So the story of the synergy of these two tools is just a theory, for now.


poma