From nobody@FreeBSD.org  Thu Apr  1 16:42:16 2010
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 823DC1065674
	for <freebsd-gnats-submit@FreeBSD.org>; Thu,  1 Apr 2010 16:42:16 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id 7111F8FC1C
	for <freebsd-gnats-submit@FreeBSD.org>; Thu,  1 Apr 2010 16:42:16 +0000 (UTC)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.3/8.14.3) with ESMTP id o31GgGT4057822
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 1 Apr 2010 16:42:16 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.3/8.14.3/Submit) id o31GgG31057821;
	Thu, 1 Apr 2010 16:42:16 GMT
	(envelope-from nobody)
Message-Id: <201004011642.o31GgG31057821@www.freebsd.org>
Date: Thu, 1 Apr 2010 16:42:16 GMT
From: James McNaughton <bitbucket63-it@yahoo.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: dhclient fails to get IP address when used with wpa-psk
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         145269
>Category:       bin
>Synopsis:       dhclient(8) fails to get IP address when used with wpa-psk
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Apr 01 16:50:07 UTC 2010
>Closed-Date:    
>Last-Modified:  Mon Apr 05 03:53:45 UTC 2010
>Originator:     James McNaughton
>Release:        8-STABLE
>Organization:
Dewey, Cheatham, & Howe
>Environment:
FreeBSD jamestown-p4.gateway.2wire.net 8.0-STABLE FreeBSD 8.0-STABLE #2: Mon Mar 29 23:19:44 CDT 2010     root@jamestown-p4.gateway.2wire.net:/usr/obj/usr/src/sys/JAMESTOWN_8_noaudio  i386
>Description:
dhclient fails to assign an IP address to wlan0. The WAP is using wpa-psk
for security and wpa_supplicant successfully associates to the AP. Wait
time on the machine in question exceeded 12 hours without the interface
being assigned an IP address. Using "/etc/rc.d/netif restart" failed to
resolve the issue.

tcpdump on the wlan0 interface showed it to be operational, outputting
broadcast packets between the AP and other hosts on the network.

A lease file for the wlan0 interface was apparently successfully created,
and showed the expected information for the network, including host IP
address, nameserver address, etc.

Forum postings suggested using synchronous dhcp and some reported success.
However on this machine that technique resulted in the system hanging on
boot waiting for dhclient. Research into dhclient configuration yielded
no suggestions for resolution.
>How-To-Repeat:
Configure the wireless interface to use WPA and DHCP and reboot.
>Fix:
A successful workaround is to configure the interface for WPA and static IP thus:
ifconfig_wlan0="WPA inet x.x.x.x/24"
and adding the appropriate information to resolv.conf.

A multihomed system may need to have the default route explicitly defined in rc.conf:
defaultrouter="x.x.x.x"


>Release-Note:
>Audit-Trail:
>Unformatted:
