ORBIT-USER: BSSID/IBSS madwifi idea?

[chris at orderonenetworks.com]

Kishore,

I'll look into pseudo-IBSS a bit more. I read a bit about while building
my recent solution. Basically, it turns of all beaconing, etc. I disliked
it since it seemed as it if wouldn't play well with other non-modified
nodes in either AP or ADHOC mode. Especially since AP nodes looking for a
channel examine beacons to decide who's using a particular channel.
Although if nothing else was running in your radio space, pseudo-IBSS
would of course be fine.

If the solution I'm proposing ends up not working, I'll definitely spend
more time looking at pseudo-IBSS.

Thanks for tip,
Chris


> Hi Chris:
>
> On the same front, madwifi-ng (v0.9.1 and v0.9.2) has a pseudo-IBSS mode
> (setup using the ahdemo option with wlanconfig). The way this works is
> that if you are on the same channel, you can hear each other - however, I
> do not know whether the code in this part of madwifi-ng has been tested as
> thoroughly as regular infrastructure mode.
>
> I feel this is another option worth considering.
>
> regards,
> Kishore
>
> ---------------------------------------------------------------------------
> Kishore Ramachandran
> Graduate Assistant, WINLAB/ECE, Rutgers University.
> WWW  : http://www.winlab.rutgers.edu/~kishore
> ---------------------------------------------------------------------------
>
> On Thu, 24 Aug 2006 chris at orderonenetworks.com wrote:
>
>> 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
>>>>
>>>
>>
>>
>>
>