From: Berat <berat@autistici.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] encapsulated ethernet frame format
Date: Wed, 22 Jul 2015 16:59:37 +0200 [thread overview]
Message-ID: <55AFAFD9.808@autistici.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1113 bytes --]
Hi,
I was trying to understand how batman-adv encapsulates ethernet frames.
Batman dissector of wireshark, shows an ethernet II section, then a
batman section, then again an ethernet II section. Is this
rappresentation respects the original capsulated header format? I
couldn't find a scheme that shows fields of an encapsulated header in
the documentation. So with wireshark, it tells me something like that:
-----------------------------------------------------------------------
Dst.Mac|Src.Mac|Type|Packt Type|Version|TTL|Seq.No|Dst.Mac|Src.Mac|Type
-----------------------------------------------------------------------
\___________________/\____________________________/\__________________/
First Ethernet Batman Section Second Ethernet
II Section II Section
Why there are two times destination and source mac addresses? I want to
retrieve mac addresses of originators of packets by working on raw
packet data. But i'm a little bit confused with this scheme. Sorry if
it's a banal question, i don't have much experience with networking.
Thanks for any help.
[-- Attachment #1.2: 0x9763E522.asc --]
[-- Type: application/pgp-keys, Size: 13764 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next reply other threads:[~2015-07-22 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 14:59 Berat [this message]
2015-07-22 15:58 ` [B.A.T.M.A.N.] encapsulated ethernet frame format Simon Wunderlich
2015-07-23 15:47 ` Berat
2015-07-25 16:15 ` Simon Wunderlich
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=55AFAFD9.808@autistici.org \
--to=berat@autistici.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.