On Fri, 2017-11-03 at 04:42 +0900, Masashi Honma wrote:
On 2017/11/01 17:10, Masashi Honma wrote: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 ?I found the reason why the dhcpv4 fails. The execution of /usr/libexec/nm-dhcp-helper fails because the binary file is at the /usr/lib/NetworkManager/nm-dhcp-helper on Ubuntu 16.04. So I used --libexecdir=, then execution error solved but still dhcpv4 fails... ./autogen.sh --prefix=/usr --sysconfdir=/etc -- localstatedir=/var --libexecdir=/usr/lib/NetworkManager
Hi, it's not clear why you would need that. When you build NM from source, you also build and install nm-dhcp- helper (in libexecdir, whatever that directory is). And if you run NetworkManager, it will spawn dhclient in a way that makes use of the right nm-dhcp-helper.
Now, I switched to Fedora 26 and it works !
ok, good then :) Thomas
Attachment:
signature.asc
Description: This is a digitally signed message part