public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Antonio Quartulli <antonio@open-mesh.com>,
	Antonio Quartulli <ordex@autistici.org>
Subject: Re: [B.A.T.M.A.N.] [PATCHv2] batctl: create common header for ICMP packets
Date: Wed, 29 May 2013 16:06:34 +0800	[thread overview]
Message-ID: <201305291606.34646.lindner_marek@yahoo.de> (raw)
In-Reply-To: <1369814304-2852-1-git-send-email-ordex@autistici.org>

On Wednesday, May 29, 2013 15:58:24 Antonio Quartulli wrote:
> From: Antonio Quartulli <antonio@open-mesh.com>
> 
> the icmp and the icmp_rr packets share the same initial
> fields since they use the same code to be processed and
> forwarded.
> 
> Extract the common fields and put them into a separate
> struct so that future ICMP packets can be easily added
> without bloating the packet definition.
> 
> However, keep the seqno field outside of the newly created
> common header because future ICMP types may require a
> bigger sequence number space.
> 
> This change breaks compatibility due to fields reordering
> in the ICMP headers.
> 
> Signed-off-by: Antonio Quartulli <antonio@open-mesh.com>
> ---
> 
> v2:
> - added changes to packet.h
> 
>  packet.h     | 38 ++++++++++++++++++++++++++++----------
>  ping.c       | 24 ++++++++++++++----------
>  tcpdump.c    | 27 +++++++++++++++++----------
>  traceroute.c | 31 +++++++++++++++++++------------
>  4 files changed, 78 insertions(+), 42 deletions(-)

Applied in revision 9ffe18f.

Thanks,
Marek

      reply	other threads:[~2013-05-29  8:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29  7:58 [B.A.T.M.A.N.] [PATCHv2] batctl: create common header for ICMP packets Antonio Quartulli
2013-05-29  8:06 ` 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=201305291606.34646.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --cc=antonio@open-mesh.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=ordex@autistici.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