Re: dhcp client support broken on karmic with latest NM build
- From: Dan Williams <dcbw redhat com>
- To: Alessandro Bono <alessandro bono gmail com>
- Cc: networkmanager-list gnome org
- Subject: Re: dhcp client support broken on karmic with latest NM build
- Date: Fri, 26 Feb 2010 15:53:52 -0800
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.
Dan
>
> >
> > Dan
> >
> > > Feb 26 10:30:31 champagne NetworkManager: <info> starting...
> > > Feb 26 10:30:31 champagne NetworkManager: <info> modem-manager is now available
> > > Feb 26 10:30:31 champagne NetworkManager: SCPlugin-Ifupdown: init!
> > > Feb 26 10:30:31 champagne NetworkManager: SCPlugin-Ifupdown: update_system_hostname
> > > Feb 26 10:30:31 champagne NetworkManager: SCPluginIfupdown: management mode: unmanaged
> > > Feb 26 10:30:31 champagne NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:19.0/net/eth0, iface: eth0)
> > > Feb 26 10:30:31 champagne NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:19.0/net/eth0, iface: eth0): no ifupdown configuration found.
> > > Feb 26 10:30:31 champagne NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:10:00.0/net/wlan0, iface: wlan0)
> > > Feb 26 10:30:31 champagne NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:10:00.0/net/wlan0, iface: wlan0): no ifupdown configuration found.
> > > Feb 26 10:30:31 champagne NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo)
> > > Feb 26 10:30:31 champagne NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
> > > Feb 26 10:30:31 champagne NetworkManager: SCPlugin-Ifupdown: end _init.
> > > Feb 26 10:30:31 champagne NetworkManager: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list.
> > > Feb 26 10:30:31 champagne NetworkManager: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
> > > Feb 26 10:30:31 champagne NetworkManager: <info> Found wlan radio killswitch rfkill1 (at /sys/devices/pci0000:00/0000:00:1c.1/0000:10:00.0/ieee80211/phy0/rfkill1) (driver <unknown>)
> > > Feb 26 10:30:31 champagne NetworkManager: <WARN> main(): Failed to start the DHCP manager: unknown or missing DHCP client 'dhcpcd'.
> > > Feb 26 10:30:31 champagne NetworkManager: <info> exiting (error)
> > >
> > >
> > >
> > > ii dhcp3-client 3.1.2-1ubuntu7.1 DHCP client
> > > ii dhcp3-common 3.1.2-1ubuntu7.1 common files used by all the dhcp3* packages
> > > ii dhcpcd 1:3.2.3-3ubuntu1 DHCP client for automatically configuring IP
> > >
> > > sandro champagne:~$ which dhcpcd
> > > /sbin/dhcpcd
> > >
> > >
> > > root champagne:/home/sandro# cat /etc/NetworkManager/nm-system-settings.conf
> > > # This file is installed into /etc/NetworkManager, and is loaded by
> > > # NetworkManager by default. To override, specify: '--config file'
> > > # during NM startup. This can be done by appending to DAEMON_OPTS in
> > > # the file:
> > > #
> > > # /etc/default/NetworkManager
> > > #
> > >
> > > [main]
> > > plugins=ifupdown,keyfile
> > >
> > > dhcp=dhcpcd
> > >
> > > no-auto-default=00:1a:4b:7a:9d:98,
> > >
> > > [ifupdown]
> > > managed=false
> > >
> > >
> > >
> > >
> > > > Note that with dhcpcd you won't be able to do DHCPv6 either since I
> > > > don't think it supports that.
> > > >
> > > > Dan
> > > >
> > > >
> > > > > dhclient version 4 and it seems to work. Albeit packaging it properly is
> > > > > beyond my debian packaging capabilities ...
> > > > >
> > > > > Regards,
> > > > > Torsten
> > > > >
> > > > > On Thu, 2010-02-25 at 14:04 +0100, Alessandro Bono wrote:
> > > > > > Hi all
> > > > > >
> > > > > > Today my machine it's not able to take an ip from either wifi or
> > > > > > ethernet, looking at log there is this message
> > > > > >
> > > > > > Feb 25 10:08:41 champagne NetworkManager: Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
> > > > > > Feb 25 10:08:41 champagne dhclient: Internet Systems Consortium DHCP Client V3.1.2
> > > > > > Feb 25 10:08:41 champagne dhclient: Copyright 2004-2008 Internet Systems Consortium.
> > > > > > Feb 25 10:08:41 champagne dhclient: All rights reserved.
> > > > > > Feb 25 10:08:41 champagne dhclient: For info, please visit http://www.isc.org/sw/dhcp/
> > > > > > Feb 25 10:08:41 champagne dhclient: Usage: dhclient [-1dqrx] [-nw] [-p <port>] [-s server]
> > > > > > Feb 25 10:08:41 champagne dhclient: [-cf config-file] [-lf lease-file][-pf pid-file] [-e VAR=val]
> > > > > > Feb 25 10:08:41 champagne dhclient: [-sf script-file] [interface]
> > > > > > Feb 25 10:08:41 champagne NetworkManager: <info> dhclient started with pid 8817
> > > > > > Feb 25 10:08:41 champagne NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) scheduled...
> > > > > > Feb 25 10:08:41 champagne NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
> > > > > > Feb 25 10:08:41 champagne NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) started...
> > > > > > Feb 25 10:08:41 champagne NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) complete.
> > > > > >
> > > > > >
> > > > > > so seems that yesterday update broke dhcp support
> > > > > >
> > > > > >
> > > > > > ii network-manager 0.8-0ubuntu4~nmt4~karmic network management framework daemon
> > > > > > ii network-manager-dev 0.8-0ubuntu4~nmt4~karmic network management framework (development fi
> > > > > > ii network-manager-gnome 0.8-0ubuntu3~nmt2~karmic network management framework (GNOME frontend
> > > > > > ii network-manager-openconnect 0.8~rc1-0ubuntu1~nm1~karmic network management framework (Openconnect pl
> > > > > > ii network-manager-openvpn 0.8~rc1-0ubuntu1~nm1~karmic network management framework (OpenVPN plugin
> > > > > > ii network-manager-pptp 0.8-0ubuntu2~nmt1~karmic network management framework (PPTP plugin)
> > > > > > ii network-manager-strongswan 1.1.1-2ubuntu1 network management framework (strongSwan plu
> > > > > > ii network-manager-vpnc 0.8-0ubuntu2~nmt1~karmic network management framework (VPNC plugin)
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > NetworkManager-list mailing list
> > > > > NetworkManager-list gnome org
> > > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > >
> > > >
> > >
> > >
> >
> >
>
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
