On 10/12/12 01:29, Marek Lindner wrote:
On 10/12/2012 12:13 PM, Nicolás Echániz wrote:
Here's a blog post on this matter with related graphics: http://blog.altermundi.net/article/batman-adv-ap-mode-with-isolation-enabled...
Summary: Infrastrucutre nodes tend to "confuse" batman-adv. Every client connected to an ap will “think” that it is directly connected to every other client, which creates a mess in potential hops selection.
Guess you have to better explain your setup if you want others to understand. The phrase "the networks uses mixed adhoc and infrastructure modes" is not self-explanatory.
will do:
Our nodes are mostly TP-Link MR3220 or WR842N with a second wifi interface connected by USB (usually WN722N).
These usb dongles use ath9k_htc which is stable and performant in infrastructure mode, but not so in adhoc. So until our dear ordex :) can get the time to squash whatever bugs are preventing the dongles from performing well in adhoc, the networks are using both adhoc and infrastructure. As a result, some links are adhoc and others are not.
The infrastructure links are the ones that show the behaviour described: all clients of an AP believe they are neighbors, and isolation so far seems to prevent this effectively.
The network in question covers 70% of a sparsely populated town and currently has 15 active nodes with links ranging from 0.1 to 3Km, plus a 16Km link to a neighboring city.
The images in the link provided help ilustrate the differences observed with and without isolation.
Is the setup clear enough now? or am I missing the point as to what is unclear? Please ask whatever needs to be clarified.
cheers, Nico.