ORBIT-USER: BSSID/CELL issues in ad-hoc mode

[chris at orderonenetworks.com]

Sachin,

Thanks for the help. I've spent the last little while looking through the
madwifi stuff to see if I can find a way to

a) turn off the check for BSSID on incoming packets.
b) force it to generate BSSID's that are all the same

both of these are really non-portable, etc. but I do need a solution.

Thanks,
Chris

> Hi Chris,
> I believe this functionality for Atheros is embedded in the HAL
> somewhere. In other words, this now gets us into the wireless driver
> domain (outside of ORBIT's control, unfortunately :-)
>
> If you are using ad-hoc mode, depending on how it is implemented, the
> responsibility of cell formation and maintenance is distributed and
> clearly there are some synchronization problems when the number of
> nodes goes up.. Hence, some of them start to create their own BSSID's
> for the same ESSID.
>
> .no solution yet...hence only commiserations. :-)
>
> -Sachin
>
> On 8/23/06, chris at orderonenetworks.com <chris at orderonenetworks.com> wrote:
>> I'm hoping someone can help.
>>
>> I've got most of the grid fired up and have huge problems with the
>> radio's
>> coming up with their own CELL/BSSID numbers and then changing them about
>> every 5 secs or so. This means that I am basically unable to build a
>> network in the grid. Sandbox nodes have no such problems - most likely
>> this is a size related issue.
>>
>> Is there anyway to manually set the CELL/BSSID, or have the cards ignore
>> this value so it doesn't matter?
>>
>> Thanks,
>> Chris
>>
>>
>