From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] dhcpcd failed to get a valid IP
Date: Tue, 15 Apr 2014 08:50:02 -0700 [thread overview]
Message-ID: <534D552A.3050107@candelatech.com> (raw)
In-Reply-To: <153F35912E69C446A72CF7D6417EBADE7CFC33@SPCCOREXCMBX01.AD.SPIRENTCOM.COM>
On 04/15/2014 08:15 AM, Shu, Nick wrote:
> Hi, All:
> Please help on this issue.
> I'm testing with a PCIe card with ath9k chip.
> I downloaded "backports-3.13.2-1" from backport site, rebuilt the ath9k driver to install.
> After running wpa_supplicant to associate to a 11N access point, I'm using "dhcpcd" to get IP address.
> I did it the same way when I tested a ath10k card and worked.
> But with this ath9k card, I got the error message as following:
>
> root at coast198:/# dhcpcd -d wlan2
> info, wlan2: dhcpcd 3.2.3 starting
> info, wlan2: hardware address = 04:f0:21:09:05:01
> info, wlan2: DUID = 00:01:00:01:1a:de:5c:27:00:15:61:20:24:3f
> info, wlan2: broadcasting for a lease
> debug, wlan2: sending DHCP_DISCOVER with xid 0x5428e610
> debug, wlan2: waiting for 20 seconds
> debug, wlan2: sending DHCP_DISCOVER with xid 0x5428e610
> debug, wlan2: sending DHCP_DISCOVER with xid 0x5428e610
> debug, wlan2: sending DHCP_DISCOVER with xid 0x5428e610
> debug, wlan2: sending DHCP_DISCOVER with xid 0x5428e610
> debug, wlan2: sending DHCP_DISCOVER with xid 0x5428e610
> debug, wlan2: sending DHCP_DISCOVER with xid 0x5428e610
> err, wlan2: timed out
> info, wlan2: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-wlan2.info'
> debug, wlan2: sending ARP probe #1
> debug, wlan2: sending ARP probe #2
> debug, wlan2: sending ARP probe #3
> debug, wlan2: sending ARP claim #1
> debug, wlan2: sending ARP claim #2
> warn, wlan2: using IPV4LL address 169.254.52.66
> info, wlan2: adding IP address 169.254.52.66/16
> debug, wlan2: no dns information to write
> debug, wlan2: exec "/etc/dhcpcd.sh" "/var/lib/dhcpcd/dhcpcd-wlan2.info" "new"
> debug, wlan2: forking to background
> info, wlan2: exiting
> root at coast198:/# dhcpcd.sh: interface wlan2 has been configured with new IP=169.254.52.66
>
> Can anybody tell me what's wrong here from this debug message?
> Seems DHCP server did response to discover message, but why?
Try sniffing your AP's interface to see if the discovers make it that
far..if so, then problem is not on your station most likely...
Thanks,
Ben
>
>
> Thank you!
>
> Nick Shu
>
>
> E-mail confidentiality.
> --------------------------------
> This e-mail contains confidential and / or privileged information belonging to Spirent Communications plc, its affiliates and / or subsidiaries. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution and / or the taking of any action based upon reliance on the contents of this transmission is strictly forbidden. If you have received this message in error please notify the sender by return e-mail and delete it from your system.
>
> Spirent Communications plc
> Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.
> Tel No. +44 (0) 1293 767676
> Fax No. +44 (0) 1293 767677
>
> Registered in England Number 470893
> Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.
>
> Or if within the US,
>
> Spirent Communications,
> 26750 Agoura Road, Calabasas, CA, 91302, USA.
> Tel No. 1-818-676- 2300
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2014-04-15 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 15:15 [ath9k-devel] dhcpcd failed to get a valid IP Shu, Nick
2014-04-15 15:50 ` Ben Greear [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=534D552A.3050107@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.