From owner-freebsd-wireless@FreeBSD.ORG Sun Jun 26 08:18:35 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 47B411065672; Sun, 26 Jun 2011 08:18:35 +0000 (UTC) (envelope-from zhtx10@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0EF4E8FC08; Sun, 26 Jun 2011 08:18:34 +0000 (UTC) Received: by pvg11 with SMTP id 11so3273681pvg.13 for ; Sun, 26 Jun 2011 01:18:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=A/o1WYLJDjoGLbFkrcPynCB0vJI5dJokdtaReE6F+Vw=; b=bqKU4VxPmHfAuujDIdIOawcS4q/e+sFYCy0daiPQ+m4/FxxB429EMAZhS9/TEowj9H RXxyPVqBZY6fESnjs9b+PtmFwdk3QNbonjmKvGxKGGk0JRugrGKnelvNC26rN4tKGPpf fg/3xPE77sDBQciUw/ph8nu0btpdqH37EpyoY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=dpBfIwAIkJVn7rs1EVaKh3hvXx9JM6KjBq7/qGZGLCIzMlxIQ3S1QAycvO9Rc96eT5 F/cqxJH2uOwohCYBA+StyxusX3kFCNyVE0BfWARDfkMwPVCqzdVYjgdAjr3KiQI8Ta8J PT0ru89ArGhzS97fP05HOGdOqPf7us6wvHR4s= Received: by 10.142.250.9 with SMTP id x9mr954289wfh.178.1309076314535; Sun, 26 Jun 2011 01:18:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.143.42.18 with HTTP; Sun, 26 Jun 2011 01:18:14 -0700 (PDT) In-Reply-To: References: From: =?UTF-8?B?57q15qiq5aSp5LiL?= Date: Sun, 26 Jun 2011 16:18:14 +0800 Message-ID: To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: Couldn't connect to wireless networking X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jun 2011 08:18:35 -0000 Well, you need to first see if once it's associated, it's actually working. > Ie, that the encryption key is correct, that it is staying associated, > that DHCP has run, etc. > > When it's associated, do: > > * ifconfig wlan0 > * ps -auxw | grep wpa_supplicant > * ps -auxw | grep dhclient > > Maybe it's associated but can't DHCP an IP address. > > > Adrian > > Yes, you're right. $ ifconfig wlan0 ... inet 0.0.0.0 #Oops! No IP! ... status: associated ... $ ps -auxw | grep wpa_supplicant root 395 0.0 0.3 11224 3168 ?? Ss 12:11AM 0:00.01 /usr/sbin/wpa_supplicant mike 1510 0.0 0.2 9124 1660 0 S+ 12:12AM 0:00.00 grep wpa_supplicant $ ps -auxw | grep dhclient root 1127 0.0 0.1 5828 1512 ?? Is 12:11AM 0:00.00 dhclient: wlan0[priv0] (dhclient) _dhcp 1517 0.0 0.2 5828 1600 ?? Is 12:12AM 0:00.00 dhclient: wlan0 (dhclient) root 1544 0.0 0.2 9124 1664 0 S+ 12:14AM 0:00.00 grep dhcilent Oops..