Re: dhcp client support broken on karmic with latest NM build

[Dan Williams <dcbw redhat com>]

On Fri, 2010-02-26 at 19:20 -0500, Tony Espy wrote:
> On 02/26/2010 06:53 PM, Dan Williams wrote:
> > On Sat, 2010-02-27 at 00:49 +0100, Alessandro Bono wrote:
> >> On Fri, 2010-02-26 at 15:19 -0800, Dan Williams wrote:
> >>> On Fri, 2010-02-26 at 10:47 +0100, Alessandro Bono wrote:
> >>>> On Thu, 2010-02-25 at 11:53 -0800, Dan Williams wrote:
> >>>>> On Thu, 2010-02-25 at 14:15 +0100, Torsten Spindler wrote:
> >>>>>> Hello Alessandro,
> >>>>>>
> >>>>>> the latest network-manager needs dhclient version 4, Ubuntu only ships
> >>>>>> version 3. I tried to compile network-manager with the options
> >>>>>> --with-dhclient=no --with-dhcpcd=yes
> >>>>>> but it still seems to want to use dhclient. As a test I packaged
> >>>>>
> >>>>> Those options no longer have an effect, support for *both* is included
> >>>>> at runtime and switchable via configuration.  You have three options:
> >>>>>
> >>>>> 1) Set IPv6 to "ignore" for that connection, at which point DHCPv6 won't
> >>>>> run if the RA told NM to do so
> >>>>> 2) Get dhclient v4, which has been out for years
> >>>>> 3) Set the 'dhcp' property in the [main] section of
> >>>>> nm-system-settings.conf to either "dhclient" or "dhcpcd"
> >>>>>
> >>>> Hi Dan
> >>>>
> >>>> I tried with the 3 option but NM not find dhcpcd and exit with error
> >>>
> >>> There is some build-time stuff involved, specifically if dhcpcd isn't
> >>> installed on the builder, then support won't be enabled by default.  You
> >>> can override that with:
> >>>
> >>> --with-dhcpcd=/path/to/binary
> >>>
> >>> even if /path/to/binary doesn't exist at build time.  Any idea how the
> >>> bits you have were built?
> >>
> >> I use automatic build from network-manager team ppa
> >> you can see full build here
> >> http://launchpadlibrarian.net/39701160/buildlog_ubuntu-karmic-amd64.network-manager_0.8-0ubuntu4~nmt4~karmic_FULLYBUILT.txt.gz
> >>
> >> I think these are informations that you need
> >> cd .&&  CFLAGS="-g -O2 -g -Wall -O2" CXXFLAGS="-g -O2 -g -Wall -O2"
> >> CPPFLAGS=""
> >> LDFLAGS="-Wl,-Bsymbolic-functions" /build/buildd/network-manager-0.8/./configure --build=x86_64-linux-gnu --prefix=/usr --includedir="\${prefix}/include" --mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" --sysconfdir=/etc --localstatedir=/var --libexecdir="\${prefix}/lib/network-manager" --disable-maintainer-mode --disable-dependency-tracking --srcdir=.   --with-dbus-sys=/etc/dbus-1/system.d --with-distro=debian --with-resolvconf=/sbin/resolvconf --libexecdir=/usr/lib/NetworkManager --with-pppd-plugindir=/usr/local/lib/pppd/2.4.4/ --with-crypto=nss --with-iptables=/sbin/iptables
> >
> > They probably need to add the --with-dhcpcd=/path/to/it and
> > --with-dhclient=/path/to/it options to the build and then dhcpcd could
> > be used if installed.
> >
> > asac/awe/ciphermox: should be pretty simple to do, you don't need dhcpcd
> > installed on the build system necessarily, just tell the NM configure
> > where it would be if it was there.
> 
> OK, I'll go ahead and add a bug for this...
> 
> FYI, it'll get fixed for Lucid, not sure about backport for Karmic. 
> That'll have to be up to the SRU team.

This change was landed on the 'dhcp6' branch which is on the 0.8.1
target (merged right after 0.8 was tagged), so it shouldn't apply to
Karmic unless you guys are doing very aggressive backports there.

Dan