From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] encapsulated ethernet frame format
Date: Sat, 25 Jul 2015 18:15:54 +0200 [thread overview]
Message-ID: <1458978.v9LkvYjrHL@prime> (raw)
In-Reply-To: <55B10C8B.2030902@autistici.org>
[-- Attachment #1: Type: text/plain, Size: 1917 bytes --]
Hi Berat,
please see below.
On Thursday 23 July 2015 17:47:23 Berat wrote:
> Thanks a lot for the answer. (Sorry, i didn't realized that i was
> replying to you instead of mailing list.) There is an ultimate point
> that i would like to understand. If you can help me it would be great.
>
> So, to see if i've got it right, i made this little simulation of the
> traffic:
>
>
>
> C1 C3 C4
> \ | /
> N1 - N2 - N3 - N4 - N5
> / \
> C2 C5
>
>
>
>
> Client C1 communicates with client C5, and i'm intercepting packets that
> are passing through node N3 and i see a unicast packet at the moment;
>
> the first ethernet II section has:
> source mac -> mac of N2
> dest. mac -> mac of N3
> ----------------------------
> batman section has:
> dest. mac -> mac of N5
> //here i see source mac only for batadv_unicast_4addr packets,
> //which are ARP requests. for all other packet types, including
> //dns request which is a unicast packet, there is only destination
> //(or originator if a broadcast packet)
Right, only the 4addr actually shows the source.
> ----------------------------
> the second ethernet II section has:
> source mac -> mac of C1
> dest. mac -> mac of C5
>
>
> So if i got it right, i would like to deduce, if a computer that i see
> by the packet that i intercept is local(connected to the antenna that
> i'm intercepting) or packet is just switched/forwarded by this antenna.
> But without that source mac information in batman section, it doesn't
> seem possible to me. Can i deduce it without that information?
You could try to look at the TTL in the batman-adv header - its decremented on
each hop, so you could find out the first one. Another way would be to check the
second ethernet II header and see if the source in the local table - although
there are some corner cases where this may be incorrect (e.g. when the client
roams).
Cheers,
Simon
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2015-07-25 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 14:59 [B.A.T.M.A.N.] encapsulated ethernet frame format Berat
2015-07-22 15:58 ` Simon Wunderlich
2015-07-23 15:47 ` Berat
2015-07-25 16:15 ` Simon Wunderlich [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=1458978.v9LkvYjrHL@prime \
--to=sw@simonwunderlich.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