From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 10 19:25:55 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 AA6951065676 for ; Tue, 10 Feb 2009 19:25:55 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell.rawbw.com (shell.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 9123D8FC12 for ; Tue, 10 Feb 2009 19:25:55 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from mail1.rawbw.com (mail1.rawbw.com [198.144.192.43]) by shell.rawbw.com (8.13.6/8.13.6) with ESMTP id n1AJPsEC092836; Tue, 10 Feb 2009 11:25:54 -0800 (PST) Received: from c-67-188-87-159.hsd1.ca.comcast.net (c-67-188-87-159.hsd1.ca.comcast.net [67.188.87.159]) by webmail.rawbw.com (Horde Framework) with HTTP; Tue, 10 Feb 2009 11:25:54 -0800 Message-ID: <20090210112554.15896t24mpahwggs@webmail.rawbw.com> Date: Tue, 10 Feb 2009 11:25:54 -0800 From: Yuri To: "Sam Leffler" References: <20090209143642.168421bp9jjvs7i8@webmail.rawbw.com> <4991ADB5.9050803@freebsd.org> In-Reply-To: <4991ADB5.9050803@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.2.1-RC1) 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 19:25:56 -0000 Quoting "Sam Leffler" : > You seem to say your network is open (no security). If not you need =20 > to show your network configuration. That's right, network is open (no security). > tcpdump can be used to tap traffic at 3 layers: 802.3, 802.11, and =20 > driver. It can be used to identify where packets are lost in the =20 > hierarchy (if at all). 'tcpdump -vv -i ath0' shows nothing when I run 'dhclient ath0' or 'dhcping -s 255.255.255.255'. dhclient always fails, dhcping says "no answer". But tcpdump shows traffic between other hosts on the same network. > Assuming packets are going out but not coming back you can sniff =20 > from a 3rd station to look for traffic in the air but not received. No, now packets don't seem to go out at all. I said before that packets went out when interface in fact was in 'monitor' mode. > Given how little info you posted it's virtually impossible to advise =20 > you what is wrong. When in doubt c&p real output; describing a =20 > problem often causes useful info to be left out. There is no "real output" from tcpdump, this is a problem. How to find out for example why 'sendto' call from dhcping doesn't =20 result in any packets on ath0 interface which is 'UP' and 'associated'? I used this same system to connect to other open WiFi networks without =20 the problem. So it seems to be network-specific. And it fails only for =20 certain networks. Yuri