From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 8 15:16:55 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1DD22F62; Mon, 8 Sep 2014 15:16:55 +0000 (UTC) Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) (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 C2AE01BE8; Mon, 8 Sep 2014 15:16:54 +0000 (UTC) Received: by mail-oa0-f51.google.com with SMTP id n16so10859160oag.10 for ; Mon, 08 Sep 2014 08:16:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9fW8j8o5gWwlKcukmvCZwVPZt5ZyNLtBKW0OsUq3xa0=; b=YKX4aZt10zeYS+GKXPzutu95Cbtl5pNH9fieBkWVBxWjeBqlFNiaAEkpbvbNn1F8Zt eYHTDBW4Zt0Z2g5PNGcWK94S2IpfNkpUX3S4szSmDp3BpZHvEreAysctDaMmYmp5PwSM 3Z9hNijmecNb3GcKr6P9gCbgOnrXCLIm+OhLDFctsDJBjWctNkBEgm0Xyu+3tQprPrYC ONgtb4oJHnyQskWwJDs0wewIgrzRwohlLWoyjx4eLKj4Lt3CHc8Vdw99+8Mos80sMynZ v366S6dnOoO5EIzkQuxhmw8Oaca3fUi1UIh9ZDzfGu68IYSL8epeyQpG4u6aF8qPF2EW EB2A== MIME-Version: 1.0 X-Received: by 10.182.213.7 with SMTP id no7mr32320448obc.39.1410189413906; Mon, 08 Sep 2014 08:16:53 -0700 (PDT) Received: by 10.202.82.84 with HTTP; Mon, 8 Sep 2014 08:16:53 -0700 (PDT) In-Reply-To: References: <540C751F.6050202@freebsd.org> Date: Mon, 8 Sep 2014 12:16:53 -0300 Message-ID: Subject: Re: Issues with urtwn From: Thiago Farina To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , Nathan Whitehorn 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: Mon, 08 Sep 2014 15:16:55 -0000 On Sun, Sep 7, 2014 at 11:36 PM, Adrian Chadd wrote: > Hi, > > On 7 September 2014 19:16, Thiago Farina wrote: >> On Sun, Sep 7, 2014 at 12:09 PM, 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. >> >> I think what you are relating here is what I observed recently too. >> Sorry, I'm new to FreeBSD. Just installed it recently, and I noticed >> that after I left it idle (I went to do something for some hours) for >> some time it lost the connection. Only rebooting makes it connect >> again to my network. > > Which NIC are you seeing this on? > Mine is urtwn0: Realtek RTL8187L from my Gateway laptop. -- Thiago Farina