Hi, On Sat, 2017-12-30 at 17:27 +0100, Mleman wrote:
NetworkManager 1.10 introduced a breaking change by making dhcp=internal the default instead of dhclient. Many distros pushed out NM 1.10 obviously without being aware of that change. Lots of users are reporting issues with their wifi connection etc. in support forums and lots of guesswork is happening about what is the cause.
The default plugin is decided by your distribution when building NetworkManager. That didn't change in 1.10 release. If such a change was done by your distribution and is unwanted, report a downstream bug. For example, Fedora didn't move away from dhclient, nor is it likely to do that any time soon. Because dhclient supports additional configuration from various locations like /etc/dhcp/dhclient.conf, and changing the default might break working installations on upgrade. Of course, that makes it problematic to ever change the default, which is a problem... On the other hand, if somebody relies on a particular DHCP plugin to be used, it might be resonable to require the user to explicitly configure it in NetworkManager.conf. This decision has to be made by your distribution.
As for the general issue of not properly working internal DHCP client: for me the only notable symptom is simple a timeout after 45sec when waiting for an IP. This happens on different machines with different network hardware and on wifi as well as on LAN. I have put my logs on pastebin here: https://pastebin.com/rQQbUrkv
The internal DHCP client is supposed to work well. Hence, your report is relevant (thanks). But there is not enough information in the logfile. Please consider providing a logfile with level=TRACE debug logging. See the hints at https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/contrib/fedora/rpm/NetworkManager.conf best, Thomas
Attachment:
signature.asc
Description: This is a digitally signed message part