El 10/01/2012 12:17 p.m., Marek Lindner escribió:
On Tuesday, January 10, 2012 21:14:38 gto...@inti.gob.ar wrote:
Yes, we suspected it could be a TX dma problem, because occasionally we
found that error in the logs, so we followed some openwrt tickets
related with that, but we're not sure that's the problem, and anyway it
has not been solved yet. We've also asked on ath9k list about the driver
debug files in case we could find something there, but they did't
answered, I guess it's hard to explain in a mail list. We haven't asked
to linux-wireless, maybe it would be better, since it could be something
on top of the driver.
You can post the links to the specific tickets / open bug reports here. Maybe
somebody has some information about it. Generally, the wifi lists are the
better place to discuss these bugs.
Here are the mentioned tickets:
https://dev.openwrt.org/ticket/9693
https://dev.openwrt.org/ticket/9654
We were thinking in a script that managed the stations to connect to the
different APs to avoid configuring each router manually. However we
realized that with just one managed interface, each router could connect
to only one AP, so if we wanted that every router could connect
bidirectionally to others we should use a number of managed interfaces
enough to connect to all neigbours, shouldn't we?
In any case it would be just another test to see if the results are
different.
Correct, managed/AP is a one-to-one connection. If you want a router to
connect to several APs you need an additional managed interface per
connection.
Regards,
Marek
Regards
Gabriel
