public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Marco Dalla Torre <marco.dallato@gmail.com>
Subject: Re: [B.A.T.M.A.N.] [RFCv4] [batctl] add IPv6 support to tcpdump parser
Date: Mon, 23 Dec 2013 20:28:04 +0800	[thread overview]
Message-ID: <22774167.RUYsjOVtNJ@diderot> (raw)
In-Reply-To: <1379929964-19779-1-git-send-email-marco.dallato@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 945 bytes --]

On Monday 23 September 2013 11:52:44 Marco Dalla Torre wrote:
> Extends 'tcpdump' functionality in 'batctl' to parse and report IPv6
> communications. 'batctl' now recognizes TCP, UDP packets and the most
> common ICMPv6 packet types:
>         -ECHO request and ECHO reply
>         -unreachable destination and subcases
>         -time exceeded
>         -neighbor discovery protocol 'solicit' and 'advert'
> 
> TCP and UDP parsing code has been moved from the IPv4 specific
> codepath to separate functions in order to allow reuse regardless
> the underlying protocol.
> 
> Signed-off-by: Marco Dalla Torre <marco.dallato@gmail.com>
> ---
> CHANGE FROM V3
> - fixed a string spacing issue
> To apply on fix "batctl tcpdump: Fix reported length of TCP payload"
>  tcpdump.c | 232
> ++++++++++++++++++++++++++++++++++++++++++++++++++------------ 1 file
> changed, 187 insertions(+), 45 deletions(-)

Applied in revision 35b3775.

Thanks,
Marek

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

      reply	other threads:[~2013-12-23 12:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-23  9:52 [B.A.T.M.A.N.] [RFCv4] [batctl] add IPv6 support to tcpdump parser Marco Dalla Torre
2013-12-23 12:28 ` 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=22774167.RUYsjOVtNJ@diderot \
    --to=mareklindner@neomailbox.ch \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=marco.dallato@gmail.com \
    /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