From: Marek Lindner <lindner_marek@yahoo.de>
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.] best way to piggy back data on OGM in batmand
Date: Tue, 4 Sep 2012 09:27:03 +0800 [thread overview]
Message-ID: <201209040927.04139.lindner_marek@yahoo.de> (raw)
In-Reply-To: <CA+h5VgqWxwCu3M0Y-D+Tuqyx5dj9oiduvvkiL7Op5KVoaac=Lw@mail.gmail.com>
On Tuesday, September 04, 2012 06:00:11 Dominic Follett-Smith wrote:
> Could anyone point me in the best direction for how to include some
> extra information in the OGM packet without increasing its size?
>
> Say for instance I want to send a specific value in the range [0:100]
> along with the OGM.
You wish to append additional data without increasing the size of the OGM ? I
don't see how this would be possible unless we sent useless data with OGM
today which you could replace with useful data. That is not the case.
Regards,
Marek
prev parent reply other threads:[~2012-09-04 1:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 22:00 [B.A.T.M.A.N.] best way to piggy back data on OGM in batmand Dominic Follett-Smith
2012-09-04 1:27 ` Marek Lindner [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=201209040927.04139.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--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