Date: Sun, 7 Sep 2014 19:36:27 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Thiago Farina <tfransosi@gmail.com> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>, Nathan Whitehorn <nwhitehorn@freebsd.org> Subject: Re: Issues with urtwn Message-ID: <CAJ-Vmonrxc2CY%2BLsY4jeh19MbELxDcP6iHXGCyogV_9H6%2BnwOw@mail.gmail.com> In-Reply-To: <CACnwZYfK_F4KnzsbrWnZS3sPB22HJ=v03VuhOTfFa8usFy_45w@mail.gmail.com> References: <540C751F.6050202@freebsd.org> <CACnwZYfK_F4KnzsbrWnZS3sPB22HJ=v03VuhOTfFa8usFy_45w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On 7 September 2014 19:16, Thiago Farina <tfransosi@gmail.com> wrote: > On Sun, Sep 7, 2014 at 12:09 PM, Nathan Whitehorn > <nwhitehorn@freebsd.org> 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? I don't have this problem with Intel/Atheros chips on freebsd-head. -a
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmonrxc2CY%2BLsY4jeh19MbELxDcP6iHXGCyogV_9H6%2BnwOw>