From: "Linus Lüssing" <linus.luessing@web.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] [patch] adding subgraph-feature to vis-output in dot-file-format
Date: Tue, 1 Sep 2009 22:47:02 +0200 [thread overview]
Message-ID: <20090901204702.GA9632@Linus-Debian> (raw)
In-Reply-To: <20090830195553.GA2410@pandem0nium>
[-- Attachment #1: Type: text/plain, Size: 3520 bytes --]
Ok, now with a larger setup I found two smaller problems. I didn't
have the time to look at the source code again yet, but I'll just post
the things we noticed here.
First of all, not all interfaces get added to a subgraph. As an example
vis-output I have this [0] file, but unfortunately the lines in brackets
are not there, but should to avoid splitted graphs.
Secondly, it seems that a vis-client is just sending to the
vis-server its prefered interface plus quality to a neighbour, not
all possible links plus qualities to the neighbour. As a
network-administrator I'd like to have these information as well
to be able to check if an interface might be broken for example.
Cheers, Linus
[0]:
--------
digraph {
"00:50:bf:d6:fd:b0" -> "00:22:b0:44:94:02" [label="1.0"]
"ca:5f:0b:67:03:c7" -> "00:ff:4d:f1:04:c5" [label="4.553"]
"00:50:bf:d6:fd:b0" -> "00:ff:82:74:9c:eb" [label="HNA"]
subgraph "cluster_00:50:bf:d6:fd:b0" {
"00:50:bf:d6:fd:b0" [peripheries=2]
"ca:5f:0b:67:03:c7"
}
"00:22:b0:98:87:de" -> "00:22:b0:98:87:fa" [label="1.15"]
"06:22:b0:98:87:dd" -> "06:22:b0:44:94:5d" [label="1.7"]
"00:22:b0:98:87:de" -> "00:e0:29:39:34:d7" [label="1.15"]
"06:22:b0:98:87:dd" -> "00:16:cb:ba:4a:f4" [label="HNA"]
"06:22:b0:98:87:dd" -> "00:19:d2:7a:ba:21" [label="HNA"]
"06:22:b0:98:87:dd" -> "00:ff:ca:4d:a5:e7" [label="HNA"]
"06:22:b0:98:87:dd" -> "00:22:b0:98:87:dd" [label="HNA"]
"06:22:b0:98:87:dd" -> "00:19:7e:6a:8a:27" [label="HNA"]
subgraph "cluster_06:22:b0:98:87:dd" {
( "00:22:b0:98:87:de" )
"06:22:b0:98:87:dd" [peripheries=2]
}
"00:22:b0:98:87:fa" -> "00:22:b0:98:87:de" [label="1.15"]
"06:22:b0:98:87:f9" -> "06:22:b0:44:c6:59" [label="1.3"]
"06:22:b0:98:87:f9" -> "06:22:b0:98:85:5b" [label="1.0"]
"06:22:b0:98:87:f9" -> "06:22:b0:98:8c:33" [label="1.0"]
"06:22:b0:98:87:f9" -> "00:22:b0:98:87:f9" [label="HNA"]
"06:22:b0:98:87:f9" -> "00:ff:1b:01:51:12" [label="HNA"]
subgraph "cluster_06:22:b0:98:87:f9" {
( "00:22:b0:98:87:fa" )
"06:22:b0:98:87:f9" [peripheries=2]
}
"06:22:b0:44:c6:59" -> "06:22:b0:98:87:f9" [label="1.15"]
"00:22:b0:44:c6:5a" -> "00:22:b0:98:8c:34" [label="1.85"]
"06:22:b0:44:c6:59" -> "06:22:b0:98:85:5b" [label="1.0"]
"06:22:b0:44:c6:59" -> "06:22:b0:98:8c:33" [label="1.32"]
"06:22:b0:44:c6:59" -> "00:22:b0:44:c6:59" [label="HNA"]
"06:22:b0:44:c6:59" -> "00:ff:d8:85:d7:fa" [label="HNA"]
subgraph "cluster_06:22:b0:44:c6:59" {
"06:22:b0:44:c6:59" [peripheries=2]
"00:22:b0:44:c6:5a"
}
"00:22:b0:44:94:02" -> "00:50:bf:d6:fd:b0" [label="1.15"]
"06:22:b0:44:94:01" -> "00:22:b0:44:94:01" [label="HNA"]
"06:22:b0:44:94:01" -> "00:ff:af:cb:d6:64" [label="HNA"]
subgraph "cluster_06:22:b0:44:94:01" {
( "00:22:b0:44:94:02" )
"06:22:b0:44:94:01" [peripheries=2]
}
"06:22:b0:98:85:5b" -> "06:22:b0:44:c6:59" [label="1.15"]
"06:22:b0:98:85:5b" -> "06:22:b0:98:8c:33" [label="1.62"]
"06:22:b0:98:85:5b" -> "00:ff:00:02:cb:82" [label="HNA"]
"06:22:b0:98:85:5b" -> "00:22:b0:98:85:5b" [label="HNA"]
subgraph "cluster_06:22:b0:98:85:5b" {
"06:22:b0:98:85:5b" [peripheries=2]
}
}
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2009-09-01 20:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 1:36 [B.A.T.M.A.N.] [patch] adding subgraph-feature to vis-output in dot-file-format Linus Lüssing
2009-08-30 1:59 ` Linus Lüssing
2009-08-30 7:37 ` Andrew Lunn
2009-08-30 20:23 ` Simon Wunderlich
2009-08-31 5:26 ` [B.A.T.M.A.N.] development flow Marek Lindner
2009-08-31 5:50 ` Andrew Lunn
2009-09-01 18:47 ` Marek Lindner
2009-09-02 6:18 ` Andrew Lunn
2009-09-03 6:06 ` Marek Lindner
2009-09-08 16:01 ` Andrew Lunn
2009-09-08 17:54 ` [B.A.T.M.A.N.] mailing list migration (was: development flow) Marek Lindner
2009-09-18 21:14 ` Jacob Marble
2009-09-18 21:19 ` Jacob Marble
2009-09-19 7:59 ` Andrew Lunn
2009-09-28 3:29 ` Jacob Marble
2009-09-28 3:31 ` Jacob Marble
2009-09-28 5:03 ` Andrew Lunn
2009-09-28 6:12 ` Jacob Marble
2009-09-29 5:06 ` Jacob Marble
2009-09-29 5:25 ` Andrew Lunn
2009-09-29 9:19 ` Marek Lindner
2009-09-29 15:56 ` Jacob Marble
2009-09-29 16:14 ` Sven Eckelmann
2009-09-30 5:39 ` Jacob Marble
2009-09-30 19:27 ` Marek Lindner
2009-09-29 15:38 ` Jacob Marble
2009-08-30 19:55 ` [B.A.T.M.A.N.] [patch] adding subgraph-feature to vis-output in dot-file-format Simon Wunderlich
2009-08-30 20:15 ` Andrew Lunn
2009-08-30 21:47 ` Linus Lüssing
2009-08-31 5:28 ` Andrew Lunn
2009-09-01 20:47 ` Linus Lüssing [this message]
2009-09-04 18:58 ` Linus Lüssing
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=20090901204702.GA9632@Linus-Debian \
--to=linus.luessing@web.de \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.