On Fri, Oct 30, 2009 at 8:45 PM, John Gilmore wrote:
>> I talked with one of the 802.11 experts I know. He's quite sure
>> that there should be no problem on Atheros hardware at least.
>> He has no problem transmitting arbitrary packets at arbitrary
>> times and no problem receiving packets eithe
> > I mean the clock in the 802.11 MAC sublayer. This defines the basis of
> > the timing synchronization function (TSF) which is a core part of
> > 802.11. Without synchronized clocks, nodes cannot communicate.
>
> I talked with one of the 802.11 experts I know. He's quite sure
> that there shoul
On Thu, Oct 29, 2009 at 12:17 PM, Daniel Drake wrote:
> 2009/10/26 Albert Cahalan :
>>> 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.
>>
>> How is this any different than the mesh situation?
>
> Exactly
2009/10/26 Albert Cahalan :
>> 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.
>
> How is this any different than the mesh situation?
Exactly how the XO-1 mesh functions on this level is frustratingly
unkno
On Fri, Oct 23, 2009 at 7:09 AM, Daniel Drake wrote:
> 2009/10/23 Albert Cahalan :
>> 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, unl
On Friday 23 October 2009 09:09:31 am Daniel Drake wrote:
> 2009/10/23 Albert Cahalan :
> > 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 t
On Fri, Oct 23, 2009 at 04:54:31PM +0545, Daniel Drake wrote:
> 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'
2009/10/23 Albert Cahalan :
> 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 k
Daniel Drake writes:
> Another laptop "C" comes along
> A <> C <--> B
> This laptop can see both of these independent laptops (each having
> its independent network). It can join one or the other. It cannot
> join both. Hence this XO can only communicate with A or B, but not
> both
