From owner-freebsd-wireless@FreeBSD.ORG Sun Sep 7 15:28:55 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EE7C34B3; Sun, 7 Sep 2014 15:28:55 +0000 (UTC) Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A14EF12AA; Sun, 7 Sep 2014 15:28:55 +0000 (UTC) Received: by mail-qa0-f49.google.com with SMTP id s7so9019200qap.36 for ; Sun, 07 Sep 2014 08:28:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=RaPHC7F7+uUhTfVM7ZKECSpWPaOau0y7kaA7DCbOEfI=; b=eQpFemoBFBEx/ParTQ4Do3U3197FHxV0J/F7WDMiboaaVOXgmZkRvDQICHmx3XmkxB XHuwbCLYbgVGI/rY7Ditbx5SOlk3LYq3i2bZcy/ai2E5P2QScovgz7477C7TlsXIPlKH 2oIuedmkt5NomDRZE2folOxW1MEDU/qKEQknauhE9GvK4jptn80fokhtWJUYhHucTU4A qNG8Mn1upJ5SmzBzO0HtmyLYDGpUXn1G/qxvoK0owYpaf6Qw7bei07wPt9y87m1gJ14A AZdQ89mhpD6KBkCSoOMz2jaQqtudcG+IP1RcJ8FiovRzTXA+Pc0N/zjuRtVOdaRzhUEz vasA== MIME-Version: 1.0 X-Received: by 10.140.42.17 with SMTP id b17mr22571418qga.52.1410103734851; Sun, 07 Sep 2014 08:28:54 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Sun, 7 Sep 2014 08:28:54 -0700 (PDT) In-Reply-To: <540C751F.6050202@freebsd.org> References: <540C751F.6050202@freebsd.org> Date: Sun, 7 Sep 2014 08:28:54 -0700 X-Google-Sender-Auth: 7stEoiG1mL7pLRA1q3-NIGM5VDw Message-ID: Subject: Re: Issues with urtwn From: Adrian Chadd To: Nathan Whitehorn Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 07 Sep 2014 15:28:56 -0000 On 7 September 2014 08:09, Nathan Whitehorn wrote: > I've been having some issues with connection stability in urtwn for several > months. The usual symptom is that after some period of time the connection > will apparently stall. If I'm running ping continuously, for instance, it > will at some point stop receiving replies. Then, sometime later, immediately > if I use the "reassociate" command in wpa_cli, the connection will fix > itself and all the packets I didn't get earlier get delivered at once: > hundreds of ping replies, for instance, some with time stamps minutes in the > past. No data is actually lost, though. > > I think the issue is that the driver does not actually support powersave > mode (maybe it should?) but reports to the AP that it does: > >> ifconfig wlan0 list sta (this is on the AP) > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > 80:1f:02:cc:47:a9 1 11 11M 8.5 0 5526 55712 EPS AE RSN > > I don't know enough about wireless to fix this, but the AP waiting for a > powersave poll and never getting one seems consistent with the problem. Is > there a simple way just to disable advertising this? When it next stalls, check ifconfig wlan0 and ifconfig urtwn0 - see if OACTIVE is set. I know iwn and ath had problems in the past where OACTIVE handling was plain broken (wasn't behind locks) and in an SMP, preemptive world things got gunked up. -a