public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] Stable adapters for Ad Hoc networks
Date: Wed, 4 Feb 2009 21:56:12 +0100	[thread overview]
Message-ID: <20090204205611.GA13896@pandem0nium> (raw)
In-Reply-To: <2ced936d0902041003g74679247i56b83a29b18e7dd2@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1877 bytes --]

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@open-mesh.net
> https://lists.open-mesh.net/mm/listinfo/b.a.t.m.a.n
> 

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2009-02-04 20:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04 18:03 [B.A.T.M.A.N.] Stable adapters for Ad Hoc networks Breno Jacinto
2009-02-04 20:56 ` Simon Wunderlich [this message]
2009-02-05 17:26   ` Breno Jacinto
2009-02-06  2:01     ` Marek Lindner
2009-02-06 17:25       ` Breno Jacinto
2009-02-07  2:30         ` Marek Lindner
2009-02-07 20:38           ` Breno Jacinto
2009-02-07 21:38             ` elektra
2009-02-07 22:44               ` Breno Jacinto
2009-02-08  3:50                 ` Marek Lindner
2009-02-08 11:47                   ` elektra
2009-02-09 18:31                     ` Breno Jacinto
2009-02-10  0:58                       ` [B.A.T.M.A.N.] WNDW elektra
2009-02-08  3:37             ` [B.A.T.M.A.N.] Stable adapters for Ad Hoc networks Marek Lindner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090204205611.GA13896@pandem0nium \
    --to=simon.wunderlich@s2003.tu-chemnitz.de \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox