On 23 April 2013 12:57, Petko Bordjukov wrote:
> Falling back to a ht:20- channel did considerably lower the number of stuck
> beacon messages on my AR9220. It still periodically hangs though (is this
> why ``baseband hangs?'' is listed in the wiki?).
Well, partially.
I'm seeing stuck beacons in
Falling back to a ht:20- channel did considerably lower the number of stuck
beacon messages on my AR9220. It still periodically hangs though (is this
why ``baseband hangs?'' is listed in the wiki?).
On Tue, Apr 23, 2013 at 5:45 PM, Lev Serebryakov wrote:
> Hello, Adrian.
> You wrote 23 апреля 2
Hello, Adrian.
You wrote 23 апреля 2013 г., 18:43:45:
AC> Try dropping it down to a HT20 channel.
AP or client or both? Is it enough to disable HT40 channels on
client?
--
// Black Lion AKA Lev Serebryakov
___
freebsd-wireless@freebsd.org mailing li
Try dropping it down to a HT20 channel.
adrian
On 23 April 2013 05:41, Lev Serebryakov wrote:
> Hello, Freebsd-wireless.
>
> Now my router/AP is new hardware in new case, and it is not
> overheating for sure.
> AP's WiFi card is Ubiquity SR-71E MiniPCIe card. Client is Intel
> Advanced-N ca
Hello, Freebsd-wireless.
Now my router/AP is new hardware in new case, and it is not
overheating for sure.
AP's WiFi card is Ubiquity SR-71E MiniPCIe card. Client is Intel
Advanced-N card. When AP sends stable stream of data (like RDesktop
connection from WiFi client to computer on wired network
