Wireless: DHCP IP lease attempt failed

Hi,
did an upgrade today and now I get the above error message, when trying to connect to my router with netcfg2. The exact error message is like following:
[root@tux matthias]#
[root@tux matthias]# netcfg2 home
dhcpcd: wlan0: ignoring DHCP message; no Server ID
dhcpcd: wlan0: ignoring DHCP message; no Server ID
dhcpcd: wlan0: ignoring DHCP message; no Server ID
dhcpcd: timed out
:: home up - DHCP IP lease attempt failed [FAIL]
My /etc/network.d/home looks like that:
CONNECTION="wireless"
INTERFACE=wlan0
QUIRKS=(prescan preessid)
SCAN="yes"
SECURITY="wpa"
ESSID="wirelessbox"
KEY="..."
IP="dhcp"
TIMEOUT=30
I did nothing except updating. Everything worked fine before that.
Any hints?
EDIT: I added the QUIRKS line after getting the error message, because a guy on IRC suggested that. This didn't help either.
Last edited by mamr (2009-05-11 12:46:11)

rsmarples wrote:
dhave wrote:
rsmarples wrote:You can't "turn the message off" as such. You you see the ignoring message then the DHCP packet really is ignored. So if you see that message AND dhcpcd still works with a proper IP (ie not ipv4ll) then you have 2 DHCP servers running on your network and one of them is fautly.
Thanks for the explanation. Is this a problem to have a broken DHCP server running for no purpose? Is this hurting my gas mileage or anything?
Well, you're probably better off finding the faulty router and disabling it.
dhcpcd presently selects and uses the first DHCP working reply it gets and if the server is "fixed" to send ServerID then you could get conflicting lease information.
I see I have a lot to learn. The reason it's finding two routers is that I have a modem-router and then, in another part of the house, an access point that I've configured as a repeater (actually, since it has a separate ssid, maybe it's not considered a repeater; I don't know).
When I move my laptop from my office into the living room, I often switch from connecting through the "repeater" and connect directly to the modem-router. It's at this point that I get the messages about "no server ID". So, in fact, dhcpcd is doing what it's supposed to be doing, I guess.
I need to do some reading and try to figure out if my setup could be cleaned up so as to avoid lease conflicts or whatever. When I fool with network stuff, I'm always working beyond my level of understanding. I usually just fiddle until I get things to work, which means I probably could do a lot to streamline and improve performance.

Similar Messages

  • Netcfg laptop wireless - "DHCP ip lease attempt failed"??

    hey folks. just loaded arch onto a toshiba laptop. in the process of configuring wireless, i followed the netcfg config instructions in the wiki. It worked fine the first time, but when I rebooted every subsequent time i tried to connect I get the "DHCP IP lease attempt failed" error. IN my logs i get absolutely nothing helpful - just "wlan0: rebinding lease of 172.16.0.138" and "wlan0: timed out". Of course, when I had Windows XP on the laptop it had zero problems connecting to the network, and it makes no damn sense why I was able to connect intially but each time after that it times out. My router has no problems.
    I did a forum search and someone suggested that this was because of a "bug" and to delete the file "/var/lib/dhcpcd/dhcpcd-wlan0.lease" file. I did this, and was able to connect successfully. But this is not a solution; am I really supposed to delete the lease EVERY time I reconnect/reboot the machine? Doesn't make any sense at all.
    Can ANYONE please help on this? I can post whatever config file/log info you need. This seems like it should be a simple setup, but I've come to realize nothing's ever simple in the linux world.... btw my network uses WPA2. There wasn't anything in the wiki about WPA2 (must be really really old, huh?); could this be part of the problem?

    Alternatively, try adding
    PRE_UP=' [ -e /var/lib/dhcpcd/dhcpcd-wlan0.lease ] && rm /var/lib/dhcpcd/dhcpcd-wlan0.lease '
    to the profile with the problem.
    Edit: I misspelled "dhcpcd" in the code above.
    Last edited by alexandrite (2010-08-15 14:54:33)

  • Wired "dhcp ip lease attempt failed"/no internet

    Hi, I've been using netcfg on arch for a couple months now and never had trouble with it until today, I just changed internet carrier and the guy came install the modem here and I tried to plug my laptop to it and I can't get internet. Before whenever I plugged an Ethernet cable it would connect automatically because of ifplugd. I use the profile "ethernet-dhcp" from the examples that I copied to /etc/network.d. When I plug the wire, internet doesn't work so I tried : netcfg -a : Done, netcfg ethernet-dhcp and get "dhcp ip lease attempt failed".
    I read the forums and tried some solution proposed to people with same error message but with wireless and sometimes I can connect to the profile, but I still don't have internet.
    I've plugged the cable in my eepc running win7 and it works (I'm writing this from the eepc). Also the link light flashes on the modem And on my T61 when I plug the cable in the ethernet slot. I tried a static profile with the same ip as my eepc but no joy.
    any suggestions ?
    thank you

    Hi, I've been using netcfg on arch for a couple months now and never had trouble with it until today, I just changed internet carrier and the guy came install the modem here and I tried to plug my laptop to it and I can't get internet. Before whenever I plugged an Ethernet cable it would connect automatically because of ifplugd. I use the profile "ethernet-dhcp" from the examples that I copied to /etc/network.d. When I plug the wire, internet doesn't work so I tried : netcfg -a : Done, netcfg ethernet-dhcp and get "dhcp ip lease attempt failed".
    I read the forums and tried some solution proposed to people with same error message but with wireless and sometimes I can connect to the profile, but I still don't have internet.
    I've plugged the cable in my eepc running win7 and it works (I'm writing this from the eepc). Also the link light flashes on the modem And on my T61 when I plug the cable in the ethernet slot. I tried a static profile with the same ip as my eepc but no joy.
    any suggestions ?
    thank you

  • Netcfg WirelesLAN gives error "DHCP IP lease attempt failed" [SOLVED]

    i couldn't find a solution for this on the forums, though it seems to be a well known problem ...
    the drivers for my network device eth1 (zd1211) are installed and it is detected by iwconfig after a fresh arch install.
    the file WirelessLAN is set up like this:
    CONNECTION="wireless"
    INTERFACE=eth1
    SCAN="yes"
    SECURITY="wpa"
    ESSID="..."
    KEY="..."
    IP="dhcp"
    TIMEOUT=20
    but a netcfg2 WirelessLAN gives me:
    :: WirelessLAN up                                                               [BUSY]
    DHCP IP lease attempt failed                                               [FAIL]
    any ideas ???
    Last edited by fdrebin (2008-09-28 16:13:20)

    Hi.
    I got the same problem since dhcpd was updated during the last full-system-upgrade (-Suy).
    My profile is the following:
    CONNECTION="ethernet"
    DESCRIPTION="..."
    INTERFACE=ra0
    IP="dhcp"
    DHCP_TIMEOUT="30"
    PRE_UP="ifconfig ra0 up; iwconfig ra0 essid Ranger channel 9 mode managed"
    I know that this config is very ugly, but it worked.
    I have got another config, that may look better for you, but I don't know if it works. I created it today. If I try this new profile, I get the same error.
    In the past configs like this led to other errors. So I made the ugly config above.
    CONNECTION="wireless"
    DESCRIPTION="..."
    INTERFACE=ra0
    SCAN="yes"
    SECURITY="none"
    ESSID="Ranger"
    IP="dhcp"
    DHCP_TIMEOUT=30
    Do you have any hints, how I can get more a detailed error report. Downgrading dhcpd would be a good idea, too. Any hints for that?
    Thanks for your help.
    Alpha

  • [SOLVED] netcfg DHCP IP lease attempt failed

    I'm trying to configure my network settings, I made a profile, netcfg recognizes the profile, but when it loads I get that error (DHCP IP lease attempt failed). Here is my profile...
    CONNECTION='wireless'
    INTERFACE='wlan0'
    SECURITY='none'
    ESSID='my network name'
    IP='dhcp'
    DCHP_TIMEOUT='30'
    Last edited by oldstutz (2010-07-30 18:33:54)

    jogan wrote:
    jogan wrote:
    Do you have any idea how to load the rt2860 driver from /lib/firmware/rt2860.bin?
    My attempt to load the driver with MODULES in /etc/rc.conf has been unsuccessful.
    oldstutz wrote:RaLink RT2860, and I have rt2860sta in my modules
    I've battled this issue for weeks on my notebook ... wireless worked on Arch (2009.08)
    last year.  Seems to me now the culprit maybe rt2860sta.
    OK, let's check
    lsmod | grep -i rt2860

  • DHCP IP lease attempt failed

    Hello
    I have a problem with netcfg. It works perfectly at home. However, now that I am trying to connect to another router it keeps giving me this error and I can't figure out why and how to fix.
    I have read several discussion on this forum on netcfg errors, however, none of them helped me, so I am asking here again.

    More details required - start with "wired or wireless?", then move on to "have I created a profile for the new network?".
    If wired, make sure your link lights are on, then try a static IP.
    If wireless, try a manual connection, as described in the wiki's wireless page.

  • Iwl4965, netcfg2 lease attempt failed

    I'm trying to get my iwl4965 running with netcfg2, but i keep getting stuck on the actual connection/dhcp process.  These are the packages i have installed:
    core/wireless_tools 29-2 [installed]
    Wireless Tools
    core/iwlwifi-4965-ucode 228.57.2.21-1 [installed]
    Intel wireless firmware for IPW4965 (iwlwifi driver)
    core/wpa_supplicant 0.5.10-1 [installed]
    A utility providing key negotiation for WPA wireless networks
    core/netcfg 2.0.6-1 [installed]
    Network configuration and profile scripts
    test.profile:
    CONNECTION="wireless"
    INTERFACE=wlan0
    SCAN="no"
    SECURITY="wpa"
    ESSID="Meow"
    KEY="mypasswd"
    IP="dhcp"
    TIMEOUT=20
    iwlist wlan0 scan:
    Cell 02 - Address: 00:19:CB:09:35:EE
    ESSID:"Meow"
    Mode:Master
    Channel:7
    Frequency:2.442 GHz (Channel 7)
    Quality=85/100 Signal level=-48 dBm Noise level=-127 dBm
    Encryption key:on
    IE: WPA Version 1
    Group Cipher : TKIP
    Pairwise Ciphers (1) : TKIP
    Authentication Suites (1) : PSK
    IE: IEEE 802.11i/WPA2 Version 1
    Group Cipher : TKIP
    Pairwise Ciphers (1) : CCMP
    Authentication Suites (1) : PSK
    Preauthentication Supported
    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
    6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
    36 Mb/s; 48 Mb/s; 54 Mb/s
    Extra:tsf=0000000c3c85d01a
    when i issue a netcfg2 test.profile, it's status says BUSY and stays like that indefinitely. when i then press control-c i get an extra line saying the DHCP lease failed:
    :: Meow up [BUSY]
    ^C - DHCP IP lease attempt failed [FAIL]
    dmesg:
    ADDRCONF(NETDEV_UP): wlan0: link is not ready
    wlan0: Initial auth_alg=0
    wlan0: authenticate with AP 00:19:cb:09:35:ee
    wlan0: RX authentication from 00:19:cb:09:35:ee (alg=0 transaction=2 status=0)
    wlan0: authenticated
    wlan0: associate with AP 00:19:cb:09:35:ee
    wlan0: RX AssocResp from 00:19:cb:09:35:ee (capab=0x51 status=0 aid=2)
    wlan0: associated
    ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    wlan0: no IPv6 routers present
    wlan0: deauthenticate(reason=3)
    could it be something trivial i'm missing? i've used wireless without problems before using networkmanager, but i really would like to use netcfg2 instead.

    Hello, there seems to problems with this iwl4965-driver.
    Those guys have similar problems:
    http://bbs.archlinux.org/viewtopic.php?id=53300
    and here is another problem with this driver described:
    http://bbs.archlinux.org/viewtopic.php? … 42#p396142
    So, it seems as these problems are related, so just try to use an older driver version.

  • [SOLVED] netcfg "IP lease attempt failed" on ethernet connection

    Since the latest update today I can't connect to the Internet (using an ethernet cable) any more.
    # NETCFG_DEBUG="yes" netcfg cable
    DEBUG: Loading profile cable
    DEBUG: Configuring interface eth0
    :: cable up [BUSY]
    DEBUG: status reported to profile_up as:
    DEBUG: Loading profile cable
    DEBUG: Configuring interface eth0
    DEBUG: ethernet_iproute_up ifup
    DEBUG: ethernet_up dhcpd -qL -t 30 eth0
    DEBUG:
    > DHCP IP lease attempt failes.
    DEBUG: profile_up connect failed
    [FAIL]
    System: Arch 64
    Does anyone have any idea what might be wrong? Not sure where to start there, as the interface eth0 seems to be up and all right under ifconfig.
    Thanks for any hints.
    Last edited by JackH79 (2011-12-01 00:53:19)

    Thanks very much for your suggestions, ewaller.
    Weirdly enough though, this morning I came into work, plugged in the cable and, voilà, it worked straight away.
    Maybe it's just that time of the month.
    Anyway, thanks again to you and cybertorture. I'll mark this as solved for now.
    EDIT: Just a little follow up to make it a bit more embarassing: I just realised that it was actually the port of the switch that's broken. So thanks to ewaller for stating the obvious
    Last edited by JackH79 (2011-12-01 07:05:25)

  • Dhcp ip lease faile? netcfg

    Hey,
      I am having an issue with netcfg and my fresh install. I have always had no problem with connecting to my wifi manually at the terminal. I read the guide about getting my wifi up at boot. I have created a profile and so on. however it works 50 percent of the time? some time i boot up no problem and the others i get
    "dhcp ip lease attempt failed"
    after i boot i can connect manually?
    any help here would be great!
    Thanks
    Paul

    Try increasing the dhcp and/or carrier timeout (instructions can be found here).

  • [solved] Problems with wireless / dhcp

    I've been happily using Arch for the past two years but only recently I hit a problem I can't seem to solve on my own.
    I have a wireless network at home, with WPA encryption and suddenly one day (probably after an update) I cannot get the IP address from my router over DHCP any more. The other PC at home (with Windows) works as it used to.
    Details:
    [fijam@hp510 ~]$ cat /etc/network.d/wlan
    CONNECTION="wireless"
    INTERFACE=eth1
    SECURITY="wpa"
    ESSID="wlan"
    KEY="xxxxxxxxxxxx"
    IP="dhcp"
    TIMEOUT="30"
    DHCP_OPTIONS="-d"
    [fijam@hp510 ~]$ cat /etc/dhcpcd.conf
    # Inform the DHCP server of our hostname for DDNS.
    hostname
    # A list of options to request from the DHCP server.
    option domain_name_servers, domain_name, domain_search, host_name
    # Most distributions have NTP support.
    #option ntp_servers
    # Respect the network MTU.
    option interface_mtu
    # A ServerID is required by RFC2131.
    # Some broken DHCP servers do not send one and dhcpcd can work without it.
    # Some broken DHCP servers NAK incorrectly and do not include a ServerID
    # either so the default is to require a ServerID.
    #require dhcp_server_identifier
    # A hook script is provided to lookup the hostname if not set by the DHCP
    # server, but it should not be run by default.
    nohook lookup-hostname
    noipv4ll
    [fijam@hp510 ~]$ sudo netcfg -c wlan
    :: wlan up [BUSY]
    dhcpcd: version 5.0.6 starting
    dhcpcd: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
    dhcpcd: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
    dhcpcd: eth1: rebinding lease of 192.168.1.12
    dhcpcd: eth1: sending DHCP_REQUEST (xid 0x55befbc9), next in 3.13 seconds
    dhcpcd: eth1: sending DHCP_REQUEST (xid 0x55befbc9), next in 7.96 seconds
    dhcpcd: timed out
    - DHCP IP lease attempt failed. [FAIL]
    [fijam@hp510 ~]$ iwconfig
    lo no wireless extensions.
    eth0 no wireless extensions.
    eth1 IEEE 802.11g ESSID:"wlan"
    Mode:Managed Frequency:2.417 GHz Access Point: 00:1E:37:EF:67:60
    Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
    Retry limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    Link Quality=68/100 Signal level=-59 dBm Noise level=-89 dBm
    Rx invalid nwid:0 Rx invalid crypt:41 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:218 Missed beacon:0
    Help would be appreciated, I am really out of ideas here.
    Last edited by fijam (2009-08-06 15:35:32)

    EDIT: Actaully, dhcpcd still would not work while dhclient obtained IP without problems. I fixed the problem by adding -r <ip> to DHCP_OPTIONS in network.d file but I am still not sure why is it necessary.
    EDIT2: Today -- not working again. I increased DHCP_TIMEOUT to 60 and it eventually gets the IP. I am surprised since the link quality is 77 and it had not been necessary before.
    Last edited by fijam (2009-08-05 09:11:04)

  • Wireless dhcp issue after upgrading WLC to 7.6.100

    Hi All,
    We have upgraded our controllers to version 7.6.100. After upgrading, the access points also upgraded their version to 15.2(4)JB3. But, the problem is that after this process the APs do not get IP. It stays on this state:
    *Sep 26 03:55:36.334: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
    Not in Bound state.
    The DCHP configuration is OK, since it is working in other two controllers we have and that we are not upgrading untill this issue is solved.
    If we connect the APs via console and configure a static IP and controller's IP, the AP registers and works fine. But, the access points are located in 20 remote sites, so we would like to avoid going site by site.
    Has anyone suffered this issue and knows how to "recover" those access points?
    Thank you very mucho for your help!

    Hi,
    Thank you for your answer conraddaniel.
    But, our issue was an error on the DHCP. The DHCP server pool for the APs was configured with lease time infinite (on a Cisco 6500). After capturing the packets and debugging on the AP we realized that the AP were receiving wrong values:
    DHCP: Scan: Renewal time: 2147483647
    DHCP: Scan: Rebind time: 536870911
    So, on the AP debugging we saw:
    DHCP: Scan: Renewal time larger than Rebind time
    On Cisco documentation:
    T1 Timer(Renewal) After a certain portion of the lease time has expired, you attempt to contact the server that initially granted the lease in order to renew the lease so its IP address can still be used.
    T2 Timer(Rebinding) If renewal with the original leasing server fails, because, for example, the server was taken offline, then you ideally try to rebind to any active DHCP server and try to extend its current lease with any server that allows it to do so.
    These T1 and T2 timers can be any values, but must be less than the IP address lease duration. T1 Timer must be less than T2. Generally T1 is set to 50 percent of the lease duration and T2 is set to 87.5 percent of the lease duration. Use this rule to set T1 and T2 timers.
    On the previous version of the WLC, the DHCP was configured in the same way and we confirmed that the APs received same times, but they ignored those wrong values.
    The workaround was to modify the lease time of the DHCP pool (1 day). This way, both timers had valid values and the APs accepted the DHCP OFFER. We still do not know why with lease infinite these timers have wrong values (a bug?).

  • Dv6 recovery attempt fail windows 7 (64)

    I'm trying to recover my Dv6-6135dx (windows 7-64 bit) using the 3 HP provided recovery DVDs. The recovery process almost completes until I get the "recovery attempt failed" message. I've retried several times. So far I've tried to do a hard reset, set the system date to 2012, and resetted the BIOS to default settings. I read in several forums on this topic that the wireless needs to be turned on in order for the recovery to be successful. However, the light on my keyboard for the wireless adapter stays orange even though I try and turn it on. Can can anyone offer help so I can get my laptop up and running? Thanks!

    If you can read the 25 character Microsoft Windows 7 license key, you can download a Windows 7 ISO file to burn to a DVD or USB flash drive. The version  must match version that came installed on your PC as  listed on the Microsoft COA sticker attached to bottom of laptop. Such as Windows Home Premium.
    Link to the Windows 7 ISO file downloads:
    http://www.w7forums.com/threads/official-windows-7-sp1-iso-image-downloads.12325/
    You can use the Windows 7 USB/DVD installation tool to convert the ISO file you download. Link and instructions below. You need a  DVD+R or DVD -R . Or a 4 GB flash drive to use the USB method.
    http://www.microsoftstore.com/store/msusa/html/pbPage.Help_Win7_usbdvd_dwnTool#installation
    Use the 25 character key on the COA to activate the installation.
    Next go to your support and driver page to install the drivers you need.
    ******Clicking the Thumbs-Up button is a way to say -Thanks!.******
    **Click Accept as Solution on a Reply that solves your issue to help others**

  • Sep 02 20:31:01    Severity:4    DHCP Client lease rejected from IPv4 router addr , MAC addr

    Problem:
    Time Capsule kept loosing connectivity from internet modem. ISP has no records of outages.
    Logs:
    Sep 02 20:31:01    Severity:4    DHCP Client lease rejected from IPv4 <router addr>, MAC <addr>
    Resolution:
    Make sure you TC is not connected to the same coax cable that the cable box is connected to.
    Although, the system may work just fine for quite some time, eventually service will be disrupted by some device attempting to connect over and over.
    For some reason, Time Capsule doesn't perform well when a device attempts to authenticate over and over, even if they device clearly isn't part of the Access Control List or even have the correct password.
    So, in this case the the offending mac address was Scientific Atlanta Device, which was my cable box.
    Regards!

    I have seen the same issue with my iOS and Mac OS devices (iPhone and MacBook Pro). I have written my own DHCP server (http://notebook.kulchenko.com/embedded/dhcp-and-dns-servers-with-arduino) and have had troubles getting my devices to connect (Windows Vista and Ubuntu devices connect fine). I suspect that this problem happens because the DHCP Offer message is sent to a broadcast address, even though (at least in my case) the broadcast flag is off in the DHCP Discover message I see.
    Unfortunately you didn't include the Discover message, so I can't tell for sure, but if it indeed has the broadcast flag set to 0, then the server should send the response message using unicast as per DHCP spec (http://www.ietf.org/rfc/rfc2131.txt, section 4.1):
      If the broadcast bit is not set and 'giaddr' is zero and
       'ciaddr' is zero, then the server unicasts DHCPOFFER and DHCPACK
       messages to the client's hardware address and 'yiaddr' address.
    So, it seems like in this case the server may be at fault, even though it would be nice for Mac OS to accept broadcast responses (and would solve my problem too).
    Can someone confirm that Mac OS does not accept broadcast responses to DHCP Discover and DHCP Request messages? Thanks.
    Paul.

  • Not able to login PIA - An error has occurred. You may attempt to sign in again. If your attempt fails, please contact your System Administrator

    One of the user is getting the below error when the person is trying to login ELM system. what could be issue for the specific user and how do we resolve this issue?
    "Not able to login PIA - An error has occurred. You may attempt to sign in again. If your attempt fails, please contact your System Administrator"

    Its works for other users, its only happened for one specific user only?  I didn't check the APPSRV.LOG file?  what needs to be checked in APPSRV.LOG, I can ask my infra team to check, because I don't have app server access to check log file.

  • HP 2000-2b16NR Recovery Attempt Failed Windows 8 64bit

    Product Name: HP 2000-2b16NR
    Operating System: Windows 8 x64
    I was attempting to do a recovery with the discs I had bought from HP and I got this message "Recovery Attempt Failed" with options to restart recovery or view details. So I restarted the recovery and inserted disc 1 as it asked. It went through the process again and it came up with this same message "Recovery Attempt Failed". This time I clicked view details and it came up with notepad titled CTOERROR.flg with the following:
    [13:17:34.28] ChkErrBB.CMD:
    [13:17:34.28] Detect some error during PININST_BBV
    [13:17:34.28] Check C:\system.sav\logs\BurnBootWarn.log
    [13:17:34.28] or, check C:\system.sav\logs\BurnBootMerge.log
    My Hard drive is completely wiped and I can not preform a system recovery by pressing f11 and I can not access Windows.
    My question is why can I not successfully complete the recovery process?
    This question was solved.
    View Solution.

    -the tip here about changing year in BIOS may help:
    http://h30434.www3.hp.com/t5/Notebook-Operating-Systems-e-g-Windows-8-and-Software/restoration-faile...
    ******Clicking the Thumbs-Up button is a way to say -Thanks!.******
    **Click Accept as Solution on a Reply that solves your issue to help others**

Maybe you are looking for