From owner-freebsd-stable@FreeBSD.ORG Sun Dec 27 20:48:25 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7371106566B; Sun, 27 Dec 2009 20:48:25 +0000 (UTC) (envelope-from takeda@takeda.tk) Received: from chinatsu.takeda.tk (takeda-1-pt.tunnel.tserv15.lax1.ipv6.he.net [IPv6:2001:470:c:16b::2]) by mx1.freebsd.org (Postfix) with ESMTP id 76DCD8FC0A; Sun, 27 Dec 2009 20:48:25 +0000 (UTC) Received: from takeda-ws.lan (takeda-ws.lan [10.0.0.3]) (authenticated bits=0) by chinatsu.takeda.tk (8.14.3/8.14.3) with ESMTP id nBRKmLQh031283 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Sun, 27 Dec 2009 12:48:23 -0800 (PST) (envelope-from takeda@takeda.tk) Date: Sun, 27 Dec 2009 12:43:35 -0800 From: Derek Kulinski X-Priority: 3 (Normal) Message-ID: <648471541.20091227124335@takeda.tk> To: Sam Leffler In-Reply-To: <4B37BE0E.7080306@freebsd.org> References: <110163611.20091216031952@takeda.tk> <4B28D281.80706@acm.poly.edu> <1952441862.20091216103925@takeda.tk> <4B37BE0E.7080306@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: Boris Kochergin , freebsd-stable@freebsd.org Subject: Re: Problems with Atheros card and hostpd X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Dec 2009 20:48:25 -0000 Hello Sam, Sunday, December 27, 2009, 12:05:34 PM, you wrote: > I didn't see anything in the thread to point a finger at freebsd but > given the debug msg log shows "ath0" instead of "wlan0" I'm guessing > whatever version was being used was pre-8.x. I think I was the only one in thread who used FreeBSD as an AP, also that was before 7.x when I made the log. So I'm not saying it's FreeBSD specific problem, I don't even think it's a BSD problem, but perhaps some kind of incompatibility and I was hoping for some workaround. > Unlikely. Try collecting a packet trace of a failure w/ wireshark or > tcpdump from a 3rd sta and send it to me. Be sure to collect data at > the 802.11 layer (e.g. -y IEEE802_11_RADIO). You might also learn > something by enabling power save debug msgs on the ap w/ wlandebug. Well, I actually managed it to work. Since the phone was rooted I changed settings and disabled WME on the phone. I associated it and it worked. Now there's a weird thing that I don't really get. After I saw that phone was working with WME disabled, I went back and changed it to the way it originally was, I also restarted the phone. To my surprise the phone continued to work (with WME enabled), and I still don't understand why. Perhaps it stored some information necessary? I think I'll deassociate the phone and make it forget the AP and see if it works. -- Best regards, Derek mailto:takeda@takeda.tk You know it's love when you memorize her IP number to skip DNS overhead