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@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Some problems with batman-adv
Date: Tue, 15 May 2012 00:37:34 +0800 [thread overview]
Message-ID: <201205150037.35178.lindner_marek@yahoo.de> (raw)
In-Reply-To: <1337010808.2814.70.camel@E-PC-JJ>
Hi,
> I've set up the ad-hoc network with WPA-Encryption. This is working
> fine. I can access all nodes if i configure the ra0 (ralink wifi)
> interface with static ip addresses. I've done this for testing purpose
> only. Normally only the bat0 interface has an ip address.
>
> [..]
>
> # iwconfig
> lo no wireless extensions.
> dummy0 no wireless extensions.
> usb0 no wireless extensions.
> eth0 no wireless extensions.
> ra0 Ralink STA ESSID:"ceR{)|n$v#pp|fJX" Nickname:"RT2870STA"
> Mode:Ad-Hoc Frequency=2.442 GHz Cell: DE:BB:8C:08:B8:EC
> Bit Rate=36 Mb/s
> RTS thr:off Fragment thr:off
> Encryption key:D83E-521A-8B9F-7C95-3ACE-D477-****-****
the ralink driver misses one very important feature to reliably run a larger
adhoc mode cell: Assigning a manually chosen BSSID. Therefore, it would not
suprise me if you experienced "cell splits" from time to time.
To verify this theory you can watch the BSSID (Cell) field on the involved
nodes and run a continuous ping on your statically configured setup. If I am
correct you also will experience packet loss and the BSSID will change.
Regards,
Marek
next prev parent reply other threads:[~2012-05-14 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 15:53 [B.A.T.M.A.N.] Some problems with batman-adv Jochen Jägers
2012-05-14 16:37 ` Marek Lindner [this message]
2012-05-14 16:42 ` Elektra
2012-05-15 15:23 ` 3zl Trizonelabs
2012-05-15 16:24 ` Jochen Jägers
2012-05-15 18:43 ` 3zl Trizonelabs
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=201205150037.35178.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/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