From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Integrity checks for packets, who does it?
Date: Fri, 20 Nov 2015 17:37:22 +0100 [thread overview]
Message-ID: <51720781.utrOks4lLJ@sven-edge> (raw)
In-Reply-To: <CANQCUf=qAPBc7qwTgYJ3KuPZVMm9crsoYLTXKePiCx1bQJkisw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
On Friday 20 November 2015 15:42:36 Patrick Bosch wrote:
> ICMP should be encapsulated by IP, which is encapsulated by the Wi-Fi
> mac header. Now I know that batman advanced inserts it's own header.
> The question is, where exactly? Does it encapsulate the Wi-Fi mac and
> takes over the integrity check or not? Also, how does it behave in the
> case of enabled encryption? WPA2 has it's own integrity check.
Layers:
4. ICMP
3. IP
2.5: batman-adv + the original ethernet header
2. Eth/WiFi/...
1. ...
So it just doesn't know about the encryption because the encryption + MIC
happens at a lower layer.
> The reason I ask, is that in Wireshark, it appears as ICMP when I
> sniff the traffic without encryption enabled.
Wireshark (especially 2.0) can dissect/parse the batman-adv
headers/encapsulation. You should check the "Packet Details" view in wireshark
to see the different headers and the payload.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-11-20 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 14:42 [B.A.T.M.A.N.] Integrity checks for packets, who does it? Patrick Bosch
2015-11-20 16:37 ` Sven Eckelmann [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=51720781.utrOks4lLJ@sven-edge \
--to=sven@narfation.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.