public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Jochen Jägers" <jochen.jaegers@riedel-at.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 18:24:28 +0200	[thread overview]
Message-ID: <1337099068.2951.8.camel@E-PC-JJ> (raw)
In-Reply-To: <CAJuY50ycsfyTGfKHJ0RR8T8z-wA4cqRnhJn_DB1v+MvbWCPv6Q@mail.gmail.com>

Hello 3zl,

which driver/version do you use? Do you have the RT2870STA.dat
in /etc/Wireless/RT2870STA? Can you show me your settings? Maybe i
missed some important settings.

Another strange thing is, that the OGMs come in all the time. Also if i
can't connect to the node. The Originator Table looks fine all the day.
The last-seen value is between 0 and 2 seconds for every node.

-- 
Mit freundlichen Grüßen
Jochen Jägers

Dr. Riedel Automatisierungstechnik GmbH
Greifswalder Str. 4
10405 Berlin

Tel. 030/428431-48
Fax. 030/428431-99

http://www.riedel-at.de/

Geschäftsführer: Dr. Manfred Riedel
Amtsgericht Berlin Charlottenburg, HRB 39094
Umsatzsteuer-Identifikationsnummer DE 137 196 925


Am Dienstag, den 15.05.2012, 17:23 +0200 schrieb 3zl Trizonelabs:
> TP-Link TL-WN321G ( RT73/RT2xx)  works well in adhoc mode with Openwrt
> & Linux driver since 3 years.
> We do use them for mulit-radio tests on VM and native  Openwrt x86 enviroment.
> Working on SLITAZ & Debian *nix versions too
> Cell-split wasnt observed, but til today there was no vwif driver
> found,i.e. no adhoc + AP possible
> regards
> 3zl
> .
> 
> 2012/5/14 Elektra <onelektra@gmx.net>:
> > Hello Jochen -
> >
> > welcome to driver & firmware hell. This is very likely a problem related to stability issues with your WiFi interfaces. I would expect this behavior since you are using USB WiFi dongles. All USB WiFi devices depend on firmware, which is loaded when you initialize the devices. Ad-hoc mode has been neglected far and wide by the industry. Since you have to load a proprietary binary blob, which is more likely broken in ad-hoc mode rather than not, I am afraid you are out of luck. I'd love to get a USB WiFi solution in my hands that actually works in a reliable and stable manner. Unfortunately I know of none.
> >
> > If anybody has something that actually works, I'd love to know.
> >
> > Cheers,
> > Elektra


  reply	other threads:[~2012-05-15 16:24 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
2012-05-14 16:42 ` Elektra
2012-05-15 15:23   ` 3zl Trizonelabs
2012-05-15 16:24     ` Jochen Jägers [this message]
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=1337099068.2951.8.camel@E-PC-JJ \
    --to=jochen.jaegers@riedel-at.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