Re: How to start NetworkManager development

[Masashi Honma <masashi honma gmail com>]

On 2017/10/30 18:34, Thomas Haller wrote:
> Hi,
>
> check https://wiki.gnome.org/Projects/NetworkManager/Hacking
>
>
> You don't need to rebuild the applet, unless you have specific reasons
> to do so. Either don't use the applet at all (nmcli), or just use the
> one provided by your installation. Older client versions are compatible
> with newer server versions, so, the applet provided by your
> distribution will work, unless you want to work on a server version
> that is older (which would be odd to do).
>
>
> NetworkManager gets D-Bus activated. So, if you just `systemctl disable
> NetworkManager` in order to start the version that you built on your
> own, then it might be restarted again, and conflict. You could for
> example `systemctl mask NetworkManager`. See `man systemctl`.
>
>
> You can install NM in a separate path, and run it from the terminal
> with --debug option, so that it doesn't fork to background.
>
> You could configure with
>         --prefix=/opt/test \
>         --localstatedir=/var \
>         --sysconfdir=/etc \
>
> There is also --run-from-build-dir configure option, so you can run it
> from the build directory.

The built NetworkManager looks not working on my environment(Ubuntu 16.04).

I'm using commit be320e2be7a6bb8837abbe3a07981a261b1656c6.

It stops with the message "dhclient started with pid 15852".
The ethernet interface could not be assinged an IPv4 address even though
it received DHCPv4 ACK (I watched it with wireshark).

I have killed existing NetworkManager and mask it with "sudo systemctl mask
NetworkManager".
I have killed nm-applet. (This could occur even if the nm-applet is alive.)

The full messages is below.

Is there any idea ?

-------------------------
$ sudo ./src/NetworkManager --no-daemon --debug
<info>  [1509522940.3979] NetworkManager (version 1.9.3) is starting... (after a restart)
<info>  [1509522940.3980] Read config: /etc/NetworkManager/NetworkManager.conf (etc: 
default-wifi-powersave-on.conf)
<info>  [1509522940.4042] manager[0x1b69110]: monitoring kernel firmware directory '/lib/firmware'.
<info>  [1509522940.4607] hostname: hostname: using hostnamed
<info>  [1509522940.4607] hostname: hostname changed from (none) to "corei7"
<info>  [1509522940.4610] dns-mgr[0x1b5d160]: init: dns=dnsmasq, rc-manager=symlink, plugin=dnsmasq
<info>  [1509522940.4616] manager[0x1b69110]: rfkill: WiFi hardware radio set enabled
<info>  [1509522940.4616] manager[0x1b69110]: rfkill: WWAN hardware radio set enabled
<warn>  [1509522940.4857] settings: could not load plugin 'ifupdown' from file 
'/usr/lib/NetworkManager/libnm-settings-plugin-ifupdown.so': No such file or directory
<info>  [1509522940.4858] settings: loaded plugin keyfile: (c) 2007 - 2016 Red Hat, Inc.  To report bugs 
please use the NetworkManager mailing list.
<warn>  [1509522940.4858] settings: could not load plugin 'ofono' from file 
'/usr/lib/NetworkManager/libnm-settings-plugin-ofono.so': No such file or directory
<info>  [1509522940.4859] manager: rfkill: WiFi enabled by radio killswitch; enabled by state file
<info>  [1509522940.4860] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
<info>  [1509522940.4860] manager: Networking is enabled by state file
<info>  [1509522940.4861] dhcp-init: Using DHCP client 'dhclient'
<info>  [1509522940.4862] Loaded device plugin: NMBondDeviceFactory (internal)
<info>  [1509522940.4862] Loaded device plugin: NMBridgeDeviceFactory (internal)
<info>  [1509522940.4862] Loaded device plugin: NMDummyDeviceFactory (internal)
<info>  [1509522940.4863] Loaded device plugin: NMEthernetDeviceFactory (internal)
<info>  [1509522940.4863] Loaded device plugin: NMInfinibandDeviceFactory (internal)
<info>  [1509522940.4863] Loaded device plugin: NMIPTunnelDeviceFactory (internal)
<info>  [1509522940.4863] Loaded device plugin: NMMacsecDeviceFactory (internal)
<info>  [1509522940.4864] Loaded device plugin: NMMacvlanDeviceFactory (internal)
<info>  [1509522940.4864] Loaded device plugin: NMPppDeviceFactory (internal)
<info>  [1509522940.4864] Loaded device plugin: NMTunDeviceFactory (internal)
<info>  [1509522940.4864] Loaded device plugin: NMVethDeviceFactory (internal)
<info>  [1509522940.4865] Loaded device plugin: NMVlanDeviceFactory (internal)
<info>  [1509522940.4865] Loaded device plugin: NMVxlanDeviceFactory (internal)
<info>  [1509522940.4869] device (lo): carrier: link connected
<info>  [1509522940.4874] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
<info>  [1509522940.4878] device (enp2s0): carrier: link connected
<info>  [1509522940.4888] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
<info>  [1509522940.4898] keyfile: add connection in-memory (9309b806-36f1-3138-ac34-2b2271c1208a,"Wired 
connection 1")
<info>  [1509522940.4910] settings: (enp2s0): created default wired connection 'Wired connection 1'
<info>  [1509522940.4921] device (enp2s0): state change: unmanaged -> unavailable (reason 'managed', 
sys-iface-state: 'external')
<info>  [1509522940.4947] manager: (virbr0): new Bridge device (/org/freedesktop/NetworkManager/Devices/3)
<info>  [1509522940.4960] keyfile: add connection in-memory (d1fa76e1-c47b-48fc-a8ac-64c1fb9acd93,"virbr0")
<info>  [1509522940.4971] device (virbr0): state change: unmanaged -> unavailable (reason 
'connection-assumed', sys-iface-state: 'external')
<info>  [1509522940.4973] device (virbr0): state change: unavailable -> disconnected (reason 
'connection-assumed', sys-iface-state: 'external')
<info>  [1509522940.4981] device (virbr0): Activation: starting connection 'virbr0' 
(d1fa76e1-c47b-48fc-a8ac-64c1fb9acd93)
<info>  [1509522940.4989] manager: (virbr0-nic): new Tun device (/org/freedesktop/NetworkManager/Devices/4)
<info>  [1509522940.5020] device (virbr0): state change: disconnected -> prepare (reason 'none', 
sys-iface-state: 'external')
<info>  [1509522940.5025] device (enp2s0): state change: unavailable -> disconnected (reason 'none', 
sys-iface-state: 'managed')
<info>  [1509522940.5030] device (virbr0): state change: prepare -> config (reason 'none', sys-iface-state: 
'external')
<info>  [1509522940.5033] policy: auto-activating connection 'Wired connection 1'
<info>  [1509522940.5037] device (virbr0): state change: config -> ip-config (reason 'none', sys-iface-state: 
'external')
<info>  [1509522940.5057] device (virbr0): state change: ip-config -> ip-check (reason 'none', 
sys-iface-state: 'external')
<info>  [1509522940.5064] device (enp2s0): Activation: starting connection 'Wired connection 1' 
(9309b806-36f1-3138-ac34-2b2271c1208a)
<info>  [1509522940.5067] device (enp2s0): state change: disconnected -> prepare (reason 'none', 
sys-iface-state: 'managed')
<info>  [1509522940.5068] manager: NetworkManager state is now CONNECTING
<info>  [1509522940.5070] device (virbr0): state change: ip-check -> secondaries (reason 'none', 
sys-iface-state: 'external')
<info>  [1509522940.5073] device (enp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 
'managed')
<info>  [1509522940.5076] device (virbr0): state change: secondaries -> activated (reason 'none', 
sys-iface-state: 'external')
<info>  [1509522940.5504] device (virbr0): Activation: successful, device activated.
<info>  [1509522940.5515] device (enp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 
'managed')
<info>  [1509522940.5522] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
<info>  [1509522940.6180] dhcp4 (enp2s0): dhclient started with pid 15852
-------------------------

Regards,
Masashi Honma.