GNOME Bugzilla – Bug 709247
NM conflicts with "script" option of dhclient configuration
Last modified: 2014-02-05 11:22:37 UTC
dhclient.conf(5) documents "script" option. NM invokes dhclient with -sf option, providing its helper tool to be invoked. Apparently dhclient can use only one of those two, so, if an unaware user enables the "script" option ... to run dhclient-script(8) and promised hooks, suddenly the NM handled connection(s) are lost after a while.
I use 0.9.4.0-0ubuntu4.3
Ah, just found the fix in git master: commit 97990135f150237eb7d529894fb0149d9faa5f0f Author: Dan Williams <dcbw@redhat.com> Date: Wed Feb 27 14:49:25 2013 +0100 dhcp: ensure any dhclient script from dhclient.conf is ignored The config file can specify a dhclient script, which gets used instead of what NM passes on the command-line. Make sure that script gets ignored in the final dhclient config, because the script NM passes is the script that needs to be used to pass data back to NM. People may have old dhclient.conf files lying around that get picked up and we don't want any script specified there to interfere. But it didn't get to any 0.9.8 update. Adding Dan Williams to Cc to decide about inclusion in the stable branch.
Fixed in master and no more information.
cherry-picked the mentioned commit 97990135f150237eb7d529894fb0149d9faa5f0f to stable branch nm-9.8.0. http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=b34c397a4fd712fa440c791155ccadbca5d28962
(In reply to comment #4) > cherry-picked the mentioned commit 97990135f150237eb7d529894fb0149d9faa5f0f to > stable branch nm-9.8.0. > > http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=b34c397a4fd712fa440c791155ccadbca5d28962 Thanks, Thomas.