From: Andrew Lunn <andrew@lunn.ch>
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.] Changing vis output ready for mainline...
Date: Tue, 13 Oct 2009 09:54:31 +0200 [thread overview]
Message-ID: <20091013075431.GE21060@lunn.ch> (raw)
In-Reply-To: <20091012081122.GB12833@lunn.ch>
> "fe:fe:00:00:04:01" -> "fe:fe:00:00:05:01" [label="1.0"]
> "fe:fe:00:00:04:01" -> "fe:fe:00:00:03:01" [label="1.0"]
> "fe:fe:00:00:04:01" -> "00:ff:7c:3c:ec:e0" [label="HNA"]
> subgraph "cluster_fe:fe:00:00:04:01" {
> "fe:fe:00:00:04:01" [peripheries=2]
> "fe:fe:00:00:04:02"
> }
>
> I suggest something like:
>
> fe:fe:00:00:04:01 fe:fe:00:00:05:01 255 fe:fe:00:00:03:01 255 00:ff:7c:3c:ec:e0 HNA fe:fe:00:00:04:02 S
>
> In BNF something like
>
> <Primary MAC> <Doublets>
> <Doublets> ::= {<Doublet> }
> <Doublet> ::= <MAC> <Flag/Value>
> <Flag/Value> ::= <TQ_Value>|<HNA>|<Secondary>
> <TQ_Value> ::= uint8_t
> <HNA> ::= "HNA"
> <Secondary> ::= "S"
A small refinement:
<Doublets> ::= {<Doublet> ","}
Adding the comma makes the format more future proof. If in the future
we need to add more doublets, triplets, etc we can do it without
breaking backwards compatibility. If batctl finds something it does
not understand, it skips to the next , separator and keeps going.
Andrew
prev parent reply other threads:[~2009-10-13 7:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 8:11 [B.A.T.M.A.N.] Changing vis output ready for mainline Andrew Lunn
2009-10-12 11:59 ` Antoine van Gelder
2009-10-12 15:22 ` Andrew Lunn
2009-10-13 8:00 ` Andrew Lunn
2009-10-12 16:48 ` Marek Lindner
2009-10-12 21:36 ` elektra
2009-10-13 7:48 ` Andrew Lunn
2009-10-13 7:54 ` Andrew Lunn [this message]
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=20091013075431.GE21060@lunn.ch \
--to=andrew@lunn.ch \
--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