From: Marek Lindner <lindner_marek@yahoo.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: Sun, 8 Feb 2009 11:50:05 +0800 [thread overview]
Message-ID: <200902081150.05625.lindner_marek@yahoo.de> (raw)
In-Reply-To: <2ced936d0902071444q129aed4me5dab6117a2e19fb@mail.gmail.com>
Hi,
> Thanks for the information. At least now I have some background
> to work on - I already have several rt73 USB dongles, some notebooks
> with Atheros, some OpenMokos (which have atheros chipsets) and a few
> Nokia N810 tablets (which have a prism chipset).
although the Openmoko Freerunner has an Atheros chip inside it does not use
the madiwifi driver (this is the AR6001 mobile chip, in case you wonder).
> And they mentioned about some intermediate mode, called
> Pseudo-IBSS or AHdemo mode, which allows a device to set a static
> BSSID and it is supported by some drivers. I suppose we are talking
> about the same thing here, just not giving any names (?).
AHdemo is not the same as setting the BSSID in ad-hoc mode manually. As
mentioned on the page you linked to the AHdemo mode does not send any beacons.
Whereas the ad-hoc mode sends beacons with a fixed BSSID. Not sending beacons
has certain side effects:
- your network will appear being "invisible" (the normal network manager wont
show it)
- you have to manually configure the connection speed and other stuff as the
usual autonegotiation is using the beacons for that
- you will have collisions (might lead to decreased performance)
- driver compat problems (only a few drivers support this mode)
Nevertheless, it will fix your cell split problem. :-)
> When you mentioned your EEE PC, which uses an Atheros chipset,
> did you also had to set a static BSSID to the same used in the mesh
> network you use?
I think EEE PC uses the madwifi driver?! If so you can set the BSSID
statically.
Regards,
Marek
next prev parent reply other threads:[~2009-02-08 3:50 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
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 [this message]
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=200902081150.05625.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.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