wlan interface (was: first play with new XO 1.5 machines)

Andrés Ambrois andresambrois at gmail.com
Fri Oct 23 07:16:34 EDT 2009

On Friday 23 October 2009 09:09:31 am Daniel Drake wrote:
> 2009/10/23 Albert Cahalan <acahalan at gmail.com>:
> > Thus, properly done, the XO labled "C" might have either of:
> >
> > a. wlan0 to reach A, and wlan1 to reach B (same hardware)
> > b. wlan0, from which wlan0_0 and wlan0_1 are instantiated
> It can't do this, unless it has 2 independent clocks in the wifi
> hardware. I do not know of any hardware that does this.
> The issue is that A and B are both hosting their own networks, they
> are both beacon masters, spewing beacons based off their own clocks.
> C can either talk with A, by finding the beacons, adjusting its own
> clock to match. (at this point, any frames coming from B will be heard
> as noise)
> or it can adjust to B's clock, in order to speak to it (and everyone
> else who's synchronized to B). At this point, frames coming from A are
> just noise.

I agree. The radio and association limitations in wifi are not so easy to 
abstract away. 

A drop in replacement to 802.11s that might be worth looking at is batman-
adv[0]. It does proactive routing (in the spirit of Cerebro) at layer 2. 

[0] http://www.open-mesh.org/wiki/batman-adv

> Daniel


More information about the Devel mailing list