public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@web.de>
To: Sven Eckelmann <sven@narfation.org>,
	Gioacchino Mazzurco <gmazzurco89@gmail.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] batctl vd dot buggy
Date: Tue, 12 Jul 2011 02:00:20 +0200	[thread overview]
Message-ID: <20110712000020.GA31975@netfeed> (raw)
In-Reply-To: <1640517.S3sb13Hzrx@sven-desktop.home.narfation.org>

On Wed, Jul 06, 2011 at 12:27:28AM +0200, Sven Eckelmann wrote:
> On Tuesday 05 July 2011 23:29:07 Gioacchino Mazzurco wrote:
> > Good job, but what we are trying to fix is the topology visualization
> > we need that at moment
> 
> Just looked with one eye at the stuff and it seems that the data which comes 
> from the kernel module is not what you expect. For example 00:15:6d:fc:72:0b 
> isn't marked as primary or secondary.

We don't mark secondary interfaces explicitly in the raw output, a
raw row output of a primary interface contains all the
information, both that it is a primary interface and also
optionally which other secondary interfaces belong to it.

Gioacchino:
Are the interfaces 00:15:6d:fc:72:0b, 06:15:6d:7c:09:d8 and
06:15:6d:fc:71:ce primary or secondary ones?
(a primary one is the one listed in the first line of 'batctl o',
the MainIf)

And those are actually the specific ones where no
subgraph-dot-thingy has been added and no box was drawn and where
the error lies, right? Or are there more issues we missed so far
(like links, HNA entries or interfaces missing completely in the list and/or
graph for instance)?

> 
> It looks like one vis_if_list
> 
> So you can't use the module from 2.6.38 and expect that we fix it with batctl. 
> And the correct people to ask here are:
>  * Simon Wunderlich (author of the vis stuff)
>  * Linus Luessing (the person which added the subgraph stuff)
>  * Andrew Lunn (he introduced the format "vis raw" which is used in vis_data)
> 
> I don't want to touch it because it may explode in my hand. But you can also 
> try whether you are lucky and check vis_seq_print_text. It is currently overly 
> complex without any reason. It could easily use seq_file and don't do the 
> precalculation (which was necessary in /sys).... I forgot the topic.
> 
> Kind regards,
> 	Sven

  parent reply	other threads:[~2011-07-12  0:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-05 13:56 [B.A.T.M.A.N.] batctl vd dot buggy Gioacchino Mazzurco
2011-07-05 14:08 ` Sven Eckelmann
2011-07-05 14:15   ` Gioacchino Mazzurco
2011-07-05 14:28     ` Sven Eckelmann
2011-07-05 14:39       ` Gioacchino Mazzurco
2011-07-05 14:47         ` Marek Lindner
2011-07-05 15:00           ` Gioacchino Mazzurco
2011-07-05 16:05             ` Gioacchino Mazzurco
2011-07-05 16:58               ` wayne abroue
2011-07-05 21:29                 ` Gioacchino Mazzurco
2011-07-05 22:27                   ` Sven Eckelmann
2011-07-05 22:32                     ` Sven Eckelmann
2011-07-12  0:00                     ` Linus Lüssing [this message]
2011-07-13 23:51                       ` Gioacchino Mazzurco

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=20110712000020.GA31975@netfeed \
    --to=linus.luessing@web.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=gmazzurco89@gmail.com \
    --cc=sven@narfation.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