Hi,
currently ath9k is limited to at most 8 BSS in AP-Mode.
Would it be possible to increase this limit or is it a hardware
limitation?
Thanks,
M. Braun
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
Sebastian Moeller wrote:
It is a net gear WNDR3700 v2, so according to:
http://wiki.openwrt.org/toh/netgear/wndr3700 it is a Atheros AR7161 rev 2 680
MHz soc with the following wireless parts: Atheros AR9223 802.11bgn / Atheros
AR9220 802.11an.
Sure, I hope I got the right one. Now this is
Joshua Richenhagen wrote:
Dear Sujith,
I was just wondering that the patch still didn't landed upstream until
3.13-rc3. Are you holding the patch back until the firmware bug is
solved?
The patch has been merged in bluetooth-next:
Hi Sujith,
On Dec 13, 2013, at 10:27 , Sujith Manoharan suj...@msujith.org wrote:
Sebastian Moeller wrote:
It is a net gear WNDR3700 v2, so according to:
http://wiki.openwrt.org/toh/netgear/wndr3700 it is a Atheros AR7161 rev 2 680
MHz soc with the following wireless parts: Atheros AR9223
Hi,
to whom it may concern.
I'm currently using the following patch and it seems to work for me
using 12 BSS (just some short superficial testing). Not sure if
BSTUCK_THRESH modification is needed.
No warranty given ;)
Regards,
M. Braun
---
Hi all,
finally managed to change the channel width through ath9k driver. In the
main.c you can play with the channelFlags variable. You can set this to
QUARTER or HALF. I do not know if this way is correct but it works for
my case.
Greetings
Tomas
On 11/23/2013 04:18 PM, Kamran Nishat wrote:
There's a work around, yeah. Much like I've/we've described.
-adrian
On 12 December 2013 01:17, Antonio Quartulli anto...@open-mesh.com wrote:
Hi Adrian!
but as far as you know, isn't the internal Atheros driver applying any
workaround or strange hack to circumvent this problem?
Or simply
Oky!
Meanwhile you get a reply from the MAC guys I will try to test again the
check fix approach. It is really strange that I can't recognize any
corruption.
However, the problem of the TX key corruption still remains. It seems we
can't do much about that.
Cheers (and thanks a lot so far!),
On 2013-12-13 10:48, Sebastian Moeller wrote:
Hi Sujith,
On Dec 13, 2013, at 10:27 , Sujith Manoharan suj...@msujith.org wrote:
Sebastian Moeller wrote:
It is a net gear WNDR3700 v2, so according to:
http://wiki.openwrt.org/toh/netgear/wndr3700 it is a Atheros AR7161 rev 2
680
MHz soc
Hello Felix,
On Dec 13, 2013, at 17:51 , Felix Fietkau n...@openwrt.org wrote:
On 2013-12-13 10:48, Sebastian Moeller wrote:
Hi Sujith,
On Dec 13, 2013, at 10:27 , Sujith Manoharan suj...@msujith.org wrote:
Sebastian Moeller wrote:
It is a net gear WNDR3700 v2, so according to:
OK, I couldn't help myself but boot up that release. Wet paint! It
successfully brought up
the 5ghz radio, but did not manage to assign an ip address to it
(netifd bug?) and failed on the 2ghz radio utterly.
trying to restart it manually fails to bring up the 5ghz radio as well.
Here's an strace
Dave Taht wrote:
OK, I couldn't help myself but boot up that release. Wet paint! It
successfully brought up
the 5ghz radio, but did not manage to assign an ip address to it
(netifd bug?) and failed on the 2ghz radio utterly.
trying to restart it manually fails to bring up the 5ghz radio as
12 matches
Mail list logo
