[B.A.T.M.A.N.] Stable adapters for Ad Hoc networks

Breno Jacinto breno at freeunix.com.br
Thu Feb 5 17:26:34 UTC 2009


Hello Simon,

    Thanks, I was searching a bit on google about that. It's harder to
solve than I thought.

     I still wonder if setting up a static BSSID will stop the BSSID
selection algorithm from ocurring. What do you think? Have tested this
in practice?

    Setting the BSSID manually was only supported by the Atheros
chipset, which runs on my laptop. I'm also working with portable
devices, such as OpenMoko Freerunner (which is Atheros too, but I
havent checked this) and Nokia N810 (which has a prism chipset). Nokia
N810 was really buggy... whenever I tried to put one device on the
network, it started to split itself from it.

best regards,

-- 
-- 
:: Breno Jacinto ::
:: breno - at - gprt.ufpe.br ::
:: FingerPrint ::
   2F15 8A61 F566 E442 8581
   E3C0 EFF4 E202 74B7 7484
:: Persistir no difícil é a única maneira de torná-lo fácil algum dia.  ::



2009/2/4 Simon Wunderlich <simon.wunderlich at s2003.tu-chemnitz.de>:
> Hey Breno,
>
> sounds like the well known ad-hoc cell splitting problem to me. A common
> workaround is to fixate the BSSID to some pre-defined value:
>
> iwconfig athX ap 02:CA:FF:EE:BA:BE
>
> hopefully all your drivers support this. :)
>
> best regards,
>        Simon
>
> On Wed, Feb 04, 2009 at 03:03:35PM -0300, Breno Jacinto wrote:
>> Hello everyone,
>>
>>   I`m running several experiments involving ad hoc networks. I`ve
>> selected some well known-to-be-compatible adapters, such as Edimax
>> (Ralink shipset), Alfa networks (Realtek) and Atheros (madwifi).
>> Atheros is available only as built-in adapter on the equipement or as
>> a  PCI board.
>>
>>   So, I'm experiencing some instability regarding the selection of
>> the BSSID used by all the nodes. I start the network with a single
>> node, then another, then another. Now, for a couple of minutes it
>> works, bu then some nodes start losing sight of each and changing
>> their BSSIDs to a different value (and they should always use the
>> same). I'm really running out of
>> explanations of why this is happening, because these nodes are all
>> in-range of each other, and should be "pingable" directly. My main
>> suspect is the driver instability, but then I dont know of any other
>> better alternatives. I've tested the following USB adapters:
>>
>> - Edimax EW-7318USg (rt73 drivers)
>> - Alfa AWUS036H-11g
>>
>>   And the builtin adapters:
>>
>> - Atheros chipset AR5007EG
>>
>>
>> best regards,
>>
>> --
>> --
>> :: Breno Jacinto ::
>> :: breno - at - gprt.ufpe.br ::
>> :: FingerPrint ::
>>    2F15 8A61 F566 E442 8581
>>    E3C0 EFF4 E202 74B7 7484
>> :: Persistir no difícil é a única maneira de torná-lo fácil algum dia.  ::
>> _______________________________________________
>> B.A.T.M.A.N mailing list
>> B.A.T.M.A.N at open-mesh.net
>> https://lists.open-mesh.net/mm/listinfo/b.a.t.m.a.n
>>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFJigDrrzg/fFk7axYRAk8QAJ9O76YpSsZ7F4YlfGOCdVMzlgxjqQCghJWF
> 8Do0FGAC4gG9ASicOnh700g=
> =paEZ
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N at open-mesh.net
> https://lists.open-mesh.net/mm/listinfo/b.a.t.m.a.n
>
>



More information about the B.A.T.M.A.N mailing list