Hi Simon, Sven,
Thanks for your excellent help. We have 50+ sites (and a total of 1000+ nodes running in the field) for over a month, and batman-adv works perfectly, maybe I wasn't notified, but I did not hear a single failure.
We have an edge case: Our nodes are relatively closely placed, which results in 40+ neighbors for each node. And batman-adv seemingly does not work for this edge case. The issue may be that with this many 40+ neighbors, and neighbors' neighbors, ... it is complicated to calculate the route, is this the possible cause?
The resolution I can think of is that we can choose the best 12 or so (configurable) neighbors (based on signal strength). Is this choosing configurable 12 or so best neighbors the best approach? I can try to make the change, and upstream for your code-review / merge.
Thanks again.
Xuebing Wang
Hi Sven,
Thanks for asking this. It is my fault that I did not ask our QA and tell the community the details.
The syndrome is that there are randomly nodes that can not ping other nodes, it happens quite often within a day. As I changed ath_dbg() to ath_warn() to print messages before ath9k_queue_reset() in our release, we get "tx hung, resetting the chip" in dmesg (for RESET_TYPE_TX_HANG). -- I am using software encryption.
This seems pointing to that ath9k driver can not handle 40 connections for IBSS/adhoc? Based on our test, 20 connections for ath9k IBSS/adhoc are definitely ok.
Thanks. Xuebing Wang
On 2017年06月02日 15:04, Sven Eckelmann wrote:
On Freitag, 2. Juni 2017 14:57:18 CEST Xuebing Wang wrote:
And batman-adv seemingly does not work for this edge
Please define "does not work" in your setup.
Kind regards, Sven
b.a.t.m.a.n@lists.open-mesh.org
-
Sven Eckelmann -
Xuebing Wang