Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: Network-Manager Problem DHCP Lease (wrong dhclient usage?)

  1. #1
    Join Date
    Sep 2006
    Beans
    4

    Arrow SOLVED - Network-Manager Problem DHCP Lease (wrong dhclient usage?)

    if the network (lan or wlan) link comes ready the network manager obtains no dhcp ip address:

    hostname removed from log:
    Code:
    Feb 24 19:49:49  NetworkManager: <info>  (eth0): carrier now ON (device state 2)
    Feb 24 19:49:49  NetworkManager: <info>  (eth0): device state change: 2 -> 3 (reason 40)
    Feb 24 19:49:49  NetworkManager: <info>  Activation (eth0) starting connection 'Auto eth0'
    Feb 24 19:49:49  NetworkManager: <info>  (eth0): device state change: 3 -> 4 (reason 0)
    Feb 24 19:49:49  NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
    Feb 24 19:49:49  NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) started...
    Feb 24 19:49:49  NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
    Feb 24 19:49:49  NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
    Feb 24 19:49:49  NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) starting...
    Feb 24 19:49:49  NetworkManager: <info>  (eth0): device state change: 4 -> 5 (reason 0)
    Feb 24 19:49:49  NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) successful.
    Feb 24 19:49:49  NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
    Feb 24 19:49:49  NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) complete.
    Feb 24 19:49:49  NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
    Feb 24 19:49:49  NetworkManager: <info>  (eth0): device state change: 5 -> 7 (reason 0)
    Feb 24 19:49:49  NetworkManager: Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
    Feb 24 19:49:49  NetworkManager: <info>  dhclient started with pid 21139
    Feb 24 19:49:49  NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP6 Configure Get) scheduled...
    Feb 24 19:49:49  NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
    Feb 24 19:49:49  NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP6 Configure Get) started...
    Feb 24 19:49:49  NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP6 Configure Get) complete.
    Feb 24 19:49:49  dhclient: Internet Systems Consortium DHCP Client V3.1.2
    Feb 24 19:49:49  dhclient: Copyright 2004-2008 Internet Systems Consortium.
    Feb 24 19:49:49  dhclient: All rights reserved.
    Feb 24 19:49:49  dhclient: For info, please visit http://www.isc.org/sw/dhcp/
    Feb 24 19:49:49  dhclient: Usage: dhclient [-1dqrx] [-nw] [-p <port>] [-s server]
    Feb 24 19:49:49  dhclient:                 [-cf config-file] [-lf lease-file][-pf pid-file] [-e VAR=val]
    Feb 24 19:49:49  dhclient:                 [-sf script-file] [interface]
    if i run the dhclient without options it becomes a dhcp lease address:

    Code:
    :~$ sudo dhclient
    There is already a pid file /var/run/dhclient.pid with pid 20927
    killed old client process, removed PID file
    Internet Systems Consortium DHCP Client V3.1.2
    Copyright 2004-2008 Internet Systems Consortium.
    All rights reserved.
    For info, please visit http://www.isc.org/sw/dhcp/
    
    SIOCSIFFLAGS: Unknown error 132
    SIOCSIFFLAGS: Unknown error 132
    Listening on LPF/wlan0/00:1b:77:04:8a:7c
    Sending on   LPF/wlan0/00:1b:77:04:8a:7c
    Listening on LPF/eth0/00:16:d3:b2:78:a3
    Sending on   LPF/eth0/00:16:d3:b2:78:a3
    Listening on LPF/vboxnet0/0a:00:27:00:00:00
    Sending on   LPF/vboxnet0/0a:00:27:00:00:00
    Sending on   Socket/fallback
    DHCPREQUEST of 192.168.178.40 on wlan0 to 255.255.255.255 port 67
    send_packet: Network is down
    receive_packet failed on wlan0: Network is down
    DHCPREQUEST of 192.168.178.47 on eth0 to 255.255.255.255 port 67
    DHCPDISCOVER on vboxnet0 to 255.255.255.255 port 67 interval 7
    DHCPACK of 192.168.178.47 from 192.168.178.1
     * Reloading /etc/samba/smb.conf smbd only
       ...done.
    bound to 192.168.178.47 -- renewal in 379059 seconds.
    Last edited by Muschl; February 26th, 2010 at 10:47 AM. Reason: Problem solved => http://ubuntuforums.org/showpost.php?p=8882228&postcount=4

  2. #2
    Join Date
    May 2007
    Beans
    95
    Distro
    Ubuntu

    Re: Network-Manager Problem DHCP Lease (wrong dhclient usage?)

    I'm getting the same thing after an update of network-manager to 0.8-0ubuntu4~nmt4~karmic.

    Which version of network-manager are you using?

    The problem is that nm is running dhclient3 with (eg):

    /sbin/dhclient -d -4 -sf /usr/lib/NetworkManager/nm-dhcp-client.action -pf /var/run/dhclient-eth0.pid -lf /var/lib/dhcp3/dhclient-d3d99611-207b-4eb8-95d7-2f2ecc7ede1c-eth0.lease -cf /var/run/nm-dhclient-eth0.conf eth0

    and dhclient doesn't like the "-4" option.

  3. #3
    Join Date
    Feb 2010
    Beans
    1

    Re: Network-Manager Problem DHCP Lease (wrong dhclient usage?)

    Same problem!

    All of symtoms are same!

    dhcp3-client is incompatible with network-manager 0.8

  4. #4
    Join Date
    May 2007
    Beans
    95
    Distro
    Ubuntu

    Re: Network-Manager Problem DHCP Lease (wrong dhclient usage?)

    I was using the wrong PPA for network-manager. See https://bugs.launchpad.net/ubuntu/+s...94/comments/71

    I've installed NM 0.8 from that PPA (https://launchpad.net/~network-manager/+archive/ppa) and now it is working fine.

  5. #5
    Join Date
    Sep 2006
    Beans
    4

    Re: Network-Manager Problem DHCP Lease (wrong dhclient usage?)

    thx rockorequin,

    your solution fixed my problem to.

  6. #6
    Join Date
    Feb 2010
    Beans
    5

    Re: Network-Manager Problem DHCP Lease (wrong dhclient usage?)

    got the same problem... could someone tells me how to remove this buggy version of network manager and install the good one? thanks a lot!

  7. #7
    Join Date
    Feb 2010
    Beans
    5

    Re: Network-Manager Problem DHCP Lease (wrong dhclient usage?)

    Quote Originally Posted by Majino View Post
    got the same problem... could someone tells me how to remove this buggy version of network manager and install the good one? thanks a lot!
    ok i managed this... but... which version of nm do you guys have?? i'm with 0.7.998 ... is the latest?? thanks!

  8. #8
    Join Date
    Aug 2008
    Location
    Montreal, QC
    Beans
    2
    Distro
    Ubuntu Development Release

    Re: Network-Manager Problem DHCP Lease (wrong dhclient usage?)

    The incompatibility between 0.8 (actually, the current latest Git snapshot from upstream) and the current dhclient is indeed an issue with the current state of the NM trunk PPA. For those wondering, it's to attempt to improve support for IPv6. Thanks for reporting this again!

    Note that the trunk PPA is used to run daily builds of NetworkManager against Git, and thus such issues may arise from time to time -- the trunk PPA is intended to help with testing new stuff of fixes that we get from upstream.

    I'm going to try and keep the other PPA (http://launchpad.net/~network-manager/+archive/ppa) up to date with "known-good" versions of recent builds of NetworkManager.

    / Matt

  9. #9
    Join Date
    Mar 2008
    Beans
    34
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: Network-Manager Problem DHCP Lease (wrong dhclient usage?)

    Hi there
    I have no wired or wireless access on my laptop following recent nm update
    Currently posting this via my desktop
    Grateful if someone could tell me how to fix network manager issue if I can't download new files
    Cheers
    Raaj

  10. #10
    Join Date
    May 2007
    Beans
    95
    Distro
    Ubuntu

    Re: Network-Manager Problem DHCP Lease (wrong dhclient usage?)

    If network manager isn't getting a connection, you should still be able to connect on one of your network interfaces by manually running the command:

    sudo dhclient

    or, if you now the interface name, eg eth0:

    sudo dhclient eth0

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •