ORBIT-USER: BSSID/IBSS madwifi idea?

[chris at orderonenetworks.com]

Glad to hear we came up with the same idea.

I really need to get this solved, so I hope I can get it implemented in
the next few days.

If you beat me to it though, don't hesitate to send me an email :)

Chris

> Nice timing. We were just in a discussion on this topic and the same
> idea was proposed.
>
> My understanding is that the nodes are not seeing each other's beacons,
> maybe in part because of some buggy implementation or as a result of
> near simultaneous node-power-on in orbit.
>
> Anyways, for ORBIT like scenario, we agreed that a hash function was the
> solution.
>
> So please go ahead with the idea.
>
> -Pandurang
>
> chris at orderonenetworks.com wrote:
>> Hello All,
>>
>> I've spent a bunch of time reading madwifi source and google trying to
>> come up with a decent solution to the BSSID problem where it jumps
>> around
>> on me.
>>
>> I think I've come up with a solution that I'm going to try and
>> implement,
>> but I'd like to see if anyone knows if it is a bad idea, or
>> fundamentally
>> flawed from the start.
>>
>> Basically in adhoc mode each node finds the oldest BSSID it can and uses
>> that. Unfortunately this is doesn't work as advertised.
>>
>> The solution I'm thinking of implementing is simply hashing the ESSID
>> (ie.
>> iwconfig essid 'blah') into one of those XX:XX:XX:XX:XX:XX addresses and
>> then when a node is in ad-hoc mode, I'll force the BSSID to that hash.
>>
>> Since each 'tweaked' node will use the same hash function they will all
>> start off on the same BSSID. Any un-tweaked nodes will either follow
>> along
>> or do something else, but they should not be unduly affected.
>>
>> I like this solution since it appears that:
>> 1. it will not muck with un-modified nodes
>> 2. does not require any fiddling with the beaconing system, etc.
>> 3. allows different ad-hoc networks with different ESSID's to co-exist.
>>
>> I'd appretiate any thoughts, comments, etc.
>>
>> Thanks!
>> Chris
>>
>