From owner-freebsd-net@FreeBSD.ORG Thu Mar 19 15:44:31 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1AB201065759 for ; Thu, 19 Mar 2009 15:44:31 +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 C12CF8FC1B for ; Thu, 19 Mar 2009 15:44:30 +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 n2JFiTrp096611 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 19 Mar 2009 08:44:30 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <49C2685D.6040801@freebsd.org> Date: Thu, 19 Mar 2009 08:44:29 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: Matthias Apitz References: <20090317103650.GA6156@rebelion.Sisis.de> <49BF7DE4.4010804@incunabulum.net> <20090317104548.GB6182@rebelion.Sisis.de> <49BFF258.4020207@freebsd.org> <20090319144251.GA13320@rebelion.Sisis.de> In-Reply-To: <20090319144251.GA13320@rebelion.Sisis.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-DCC-sonic.net-Metrics: ebb.errno.com; whitelist Cc: freebsd-net@freebsd.org Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Mar 2009 15:44:32 -0000 Matthias Apitz wrote: > El día Tuesday, March 17, 2009 a las 11:56:24AM -0700, Sam Leffler escribió: > > >> His setup is static key wep; not wpa so I don't think wpa_supplicant is >> the issue. >> >> Matthias, your tcpdump of the dhclient packets isn't usable; please try: >> >> tcpdump -i ath0 -n -y IEEE802_11_RADIO >> >> I reviewed the driver to the code in HEAD and the only difference in the >> crypto area should not matter in this case. It's possible wme is >> somehow enabled and causing problems but the ifconfig output doesn't >> indicate that. >> >> If you can find out the model of ap that might be helpful. >> Unfortunately the best thing to try is HEAD. >> > > I will try to collect a better tcpdump of the dhclient packets on the > weekend and as well figure out what kind of model the AP is; > > would it be helpful to connect with a Windows XP laptop (which seems to > work) to gather some information of the Wifi and other network > parameters? how this could be seen in Windows? maybe there is some > special compression of the payload of the packages in place? > Having a packet trace of a working connection to compare would be very helpful. > I have seen such 'options' in another AP (a Netgear WGT624 v3), > the option was called "[ ] Disable Advanced 108Mbps Features" > and this must be checked (i.e. disabled) to make DHCP happy with > the ath0 EeePC; > That controls SuperG support in Atheros-based ap's and is unrelated. There is a known problem with SuperG support that has been fixed in HEAD but not yet backmerged. For reasons unknown your (apparently) simple setup is not working. I do not use RELENG_7 w/ the stock wireless and have no familiarity with it's status so it's more likely there's just some bug fix not back-merged. > unfortunately I can't look into the AP about this problem is :-( > > thx > > matthias >