public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
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.] problem with mesh network
Date: Tue, 10 Jan 2012 23:17:38 +0800	[thread overview]
Message-ID: <201201102317.38866.lindner_marek@yahoo.de> (raw)
In-Reply-To: <4F0C39BE.3000209@inti.gob.ar>

On Tuesday, January 10, 2012 21:14:38 gtolon@inti.gob.ar wrote:
> Yes, we suspected it could be a TX dma problem, because occasionally we
> found that error in the logs, so we followed some openwrt tickets
> related with that, but we're not sure that's the problem, and anyway it
> has not been solved yet. We've also asked on ath9k list about the driver
> debug files in case we could find something there, but they did't
> answered, I guess it's hard to explain in a mail list. We haven't asked
> to linux-wireless, maybe it would be better, since it could be something
> on top of the driver.

You can post the links to the specific tickets / open bug reports here. Maybe 
somebody has some information about it. Generally, the wifi lists are the 
better place to discuss these bugs.


> We were thinking in a script that managed the stations to connect to the
> different APs to avoid configuring each router manually. However we
> realized that with just one managed interface, each router could connect
> to only one AP, so if we wanted that every router could connect
> bidirectionally to others we should use a number of managed interfaces
> enough to connect to all neigbours,  shouldn't we?
> In any case it would be just another test to see if the results are
> different.

Correct, managed/AP is a one-to-one connection. If you want a router to 
connect to several APs you need an additional managed interface per 
connection.

Regards,
Marek

  reply	other threads:[~2012-01-10 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1326193201.4676.b.a.t.m.a.n@lists.open-mesh.org>
2012-01-10 13:14 ` [B.A.T.M.A.N.] problem with mesh network gtolon
2012-01-10 15:17   ` Marek Lindner [this message]
2012-01-11 12:52     ` gtolon
     [not found] <mailman.3.1325847602.24549.b.a.t.m.a.n@lists.open-mesh.org>
2012-01-06 15:34 ` gtolon
2012-01-09 12:22   ` 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=201201102317.38866.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