From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 1 01:19:14 2012 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 371FE1065677 for ; Sun, 1 Jan 2012 01:19:14 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id E45878FC12 for ; Sun, 1 Jan 2012 01:19:13 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so20244818vbb.13 for ; Sat, 31 Dec 2011 17:19:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=/BgFnhD9nFkGMWOo2KWvENPSpiXPhBEx3Lu7n39oVGs=; b=QyjeZw+lDNp+GZH2CmlXG2FgEl9ys9VrBLOv6+GvBywpD4kGRDPlhup3htphLHyNZm OfzwokHfbAaudq09anAhzntCOdWfqiEoQ4dGqDLK4oy0+hZ+GMEWdudUE7XBuXJP/7td urSLTp6ojHRhKsA6hEMrEcHQz+Mhn7J2LieWc= MIME-Version: 1.0 Received: by 10.52.33.99 with SMTP id q3mr20936493vdi.100.1325380753051; Sat, 31 Dec 2011 17:19:13 -0800 (PST) Received: by 10.52.36.5 with HTTP; Sat, 31 Dec 2011 17:19:13 -0800 (PST) In-Reply-To: References: Date: Sat, 31 Dec 2011 17:19:13 -0800 Message-ID: From: Adrian Chadd To: "Lay, Nathan" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-wireless@freebsd.org" Subject: Re: ath "stops working" in hostap mode 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, 01 Jan 2012 01:19:14 -0000 On 31 December 2011 17:15, Lay, Nathan wrote: > Adrian, > Thanks for the prompt response. Bumping the interface up and down does no= t fix it. Destroying and recreating the interface does not fix it either. T= he interface is completely unresponsive when this problem arises. As far as= I can tell, it does not transmit (it vanishes from view from all other dev= ices). > > I do not have ATH_ENABLE_11N compiled in. Would this improve stability? T= he interface shows that it is using 11g mode with background scanning turne= d off. Here is exactly how it is configured and used: Hi, Please don't compile in ATH_ENABLE_11N. But do add: options ATH_DEBUG options AH_DEBUG options ATH_DIAGAPI > create_args_wlan0=3D"wlanmode hostap -bgscan" > autobridge_bridge0=3D"wlan0 lan0" > > It also sits behind pf (I saw pf mentioned in a similar message about ath= ). > > I've installed athstats. Attached is the output. Ok. Can you please do this: * recompile with the above options; * try running 'athstats -i ath0 -o bexmit,bmiss 1' * (athstats -l will list what you can track, statistics-wise) * Make sure it's sending those beacons, or at least queuing to send those beacons. Once that's done, wait until it fails and then try it again. It should still be trying to send the beacons, but we'll see what else shows up. Finally, do you have any FreeBSD stations? That we could use to see what's going on in the air? Adrian