From: "Linus Lüssing" <linus.luessing@web.de>
To: "B.A.T.M.A.N" <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: Sun, 30 Aug 2009 03:59:03 +0200 [thread overview]
Message-ID: <20090830015903.GA26116@Linus-Debian> (raw)
In-Reply-To: <20090830013647.GA26017@Linus-Debian>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
And if someone prefers a visual example, a simple setup like
node1 <-> node2 <-> node3 results into a dot-file like this:
digraph {
"22:05:f9:aa:77:1f" -> "a2:14:84:e5:e5:46" [label="1.15"]
"22:05:f9:aa:77:1f" -> "00:ff:5b:62:9c:a3" [label="HNA"]
subgraph "cluster_22:05:f9:aa:77:1f" {
"22:05:f9:aa:77:1f" [peripheries=2]
}
"6a:25:1f:a0:14:72" -> "4e:18:87:ef:80:12" [label="1.0"]
"6a:25:1f:a0:14:72" -> "00:ff:2c:c8:bd:d5" [label="HNA"]
subgraph "cluster_6a:25:1f:a0:14:72" {
"6a:25:1f:a0:14:72" [peripheries=2]
}
"a2:14:84:e5:e5:46" -> "22:05:f9:aa:77:1f" [label="1.0"]
"4e:18:87:ef:80:12" -> "6a:25:1f:a0:14:72" [label="1.15"]
"a2:14:84:e5:e5:46" -> "00:ff:5e:e0:23:15" [label="HNA"]
subgraph "cluster_a2:14:84:e5:e5:46" {
"a2:14:84:e5:e5:46" [peripheries=2]
"4e:18:87:ef:80:12"
}
}
Which can then be parsed to a nice svg with fdp (or dot):
http://krtek.asta.uni-luebeck.de:8080/~tux/batman-vis-with-subgraph.svg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2009-08-30 1:59 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 [this message]
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
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=20090830015903.GA26116@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox