public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <mareklindner@neomailbox.ch>
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.] Suggestion for routing improvement on poor links
Date: Sat, 22 Feb 2014 21:20:43 +0800	[thread overview]
Message-ID: <14218846.TP5slI6GEB@diderot> (raw)
In-Reply-To: <D8FCFBAF-224C-454D-B86C-D57641FB0DF1@gmx.de>

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

On Thursday 20 February 2014 11:20:01 whangarei & opua wrote:
> The setup is like this:
> whangarei is my router, it has one Wlan link to each of this 3  
> neighbor router, MAC in the grep, hostname as comment.
> This 3 routers are in one large building (across a park) but sometimes  
> don't see each other. 2 of them have VPN connects.
> I've looked only to the next hop, by grep the lines beginning with the  
> MAC of this neighbor routers.
> The intension was to get a better feeling of the link quality then  
> with the 'iw dev wlan0-1 station dump' output.
> So i have observed this behavior...
> 
> Have attached the router output as a file, it should be more readable.

Unfortunately, the information you provided isn't comprehensive enough to 
comment on your case. Please take a look at bat-hosts to have meaningful names 
in your originator table. Furthermore, we need a clear description of your 
setup for what the routing concerns. You can take a look at our routing 
scenarios page to get a feeling what we usually work with:
http://www.open-mesh.org/projects/open-mesh/wiki/Routing_scenarios

A diagram is no must but certainly helpful.

As soon as we have a clearer understanding of how your setup looks like, you 
can explain what behavior you see and what you would expect, plus originator 
tables from each node involved.

Cheers,
Marek

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2014-02-22 13:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 20:56 [B.A.T.M.A.N.] Suggestion for routing improvement on poor links whangarei & opua
2014-02-19 21:27 ` Antonio Quartulli
2014-02-19 22:12   ` whangarei & opua
2014-02-19 22:30     ` Antonio Quartulli
2014-02-20  8:54       ` Andrew Lunn
2014-02-20  9:03         ` Antonio Quartulli
2014-02-20  9:09           ` Andrew Lunn
2014-02-20  9:44             ` Antonio Quartulli
2014-02-20 10:10               ` Andrew Lunn
2014-02-20 10:33               ` Marek Lindner
     [not found]       ` <F42F9132-14DE-4496-A715-389CF13D6C49@gmx.de>
     [not found]         ` <5305C654.5020605@meshcoding.com>
2014-02-20 10:20           ` whangarei & opua
2014-02-22 13:20             ` Marek Lindner [this message]
2014-02-23 10:35               ` whangarei & opua

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=14218846.TP5slI6GEB@diderot \
    --to=mareklindner@neomailbox.ch \
    --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