From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 10 16:39:20 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02CC710656C7 for ; Tue, 10 Feb 2009 16:39:19 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 175528FC4A for ; Tue, 10 Feb 2009 16:39:18 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n1AGdHjQ027527 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Feb 2009 08:39:17 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <4991ADB5.9050803@freebsd.org> Date: Tue, 10 Feb 2009 08:39:17 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: Yuri References: <20090209143642.168421bp9jjvs7i8@webmail.rawbw.com> In-Reply-To: <20090209143642.168421bp9jjvs7i8@webmail.rawbw.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-sonic.net-Metrics: ebb.errno.com; whitelist Cc: freebsd-hackers@freebsd.org Subject: Re: How to troubleshoot why ath0 can't connect to a passwordless wireless network? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2009 16:39:28 -0000 Yuri wrote: > I have a several wireless networks without password that my linux box > easily connects to. > > On FreeBSD 'ifconfig ath0 up scan' command shows it. 'ifconfig ath0 > ssid up' brings interface to 'associated' state. But > dhclient fails to set it up. > > I have another device on the same system: ral0. It sometimes connects > to these networks ok, sometimes has the same problem. > > What can I do to understand what may be a problem with ath0 in my case? > > I tried to use tcpdump. It shows outbound DHCP packets and nothing is > inbound. > > I asked similar question here before, somebody asked me to downgrade > atheros driver to one particular lower version. But this didn't help. > > Relevant dmesg lines are: > ath_hal: 0.9.30.13 (AR5210, AR5211, AR5212, AR5216, RF5111, RF5112, > RF2413, RF5413, RF2133) > ath0: mem 0xcffe0000-0xcffeffff irq 16 at device 5.0 on > pci0 > ath0: mac 7.8 phy 4.5 radio 5.6 > > I use 71-PRERELEASE You seem to say your network is open (no security). If not you need to show your network configuration. wlanstats shows statistics collected by the 802.11 layer. athstats show stats collected by the ath driver. Both are important tools for diagnosing problems. tcpdump can be used to tap traffic at 3 layers: 802.3, 802.11, and driver. It can be used to identify where packets are lost in the hierarchy (if at all). Assuming packets are going out but not coming back you can sniff from a 3rd station to look for traffic in the air but not received. Given how little info you posted it's virtually impossible to advise you what is wrong. When in doubt c&p real output; describing a problem often causes useful info to be left out. BTW hal version 0.9.30.13 was a test build; RELENG_7 has 0.9.20.3 and HEAD has source code for a much newer version. Sam