From: Antonio Quartulli <ordex@autistici.org>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] batman-adv: Raw Socket Communication
Date: Thu, 29 Nov 2012 00:18:24 +0100 [thread overview]
Message-ID: <20121128231824.GE32479@ritirata.org> (raw)
In-Reply-To: <CALDpWg6BczTcB3g=njyTfTHGuuKODB8AkxrLguOyH8Y3nMB5yA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2462 bytes --]
Something is not correct in your reasoning:
batctl ping/traceroute is a debug mechanism in which you make two _nodes_
communicate with each other, therefore here you use the node identifier which is
the MAC address that you can also read in batctl o output.
When you want to send _payload data_ over bat0 (and this is what your program is
trying to do), then you are acting as _client_
and your source mac address is not your ah0's address anymore but it is the one
associated to your bat0. To see it just run "ifconfig bat0" and and look at the
HWAddr info.
Cheers,
On Wed, Nov 28, 2012 at 06:09:48PM -0500, liu muye wrote:
> Besides, when do batctl ping. I am using the MAC address of ah0. I can
> ping other node.
> If the MAC address is wrong, I think I cannot even ping another node,
> or traceroute to another node.
>
> Thanks
>
> On Wed, Nov 28, 2012 at 6:02 PM, liu muye <lmy19901031@gmail.com> wrote:
> > One follow up question:
> >
> > When I do batctl o. It shows the MAC address of my network interface.
> > In my case, is ah0.
> > Not sure what to do in order to show the MAC address of the bat0.
> >
> > Thanks
> > Muye Liu
> >
> > On Tue, Nov 27, 2012 at 11:15 PM, liu muye <lmy19901031@gmail.com> wrote:
> >> Hello:
> >>
> >> This is Muye again. I have encountered another problem recently when I
> >> am using B.A.T.M.A.N to do the socket programming.
> >>
> >> Currently, I have three nodes. Namely, node A, node B, and node C. The
> >> testing environment is a hall way in our department.
> >>
> >> I put node A in one end of the hall way, node C in another end of the
> >> hall way. Node B is in the middle of the hall way.
> >>
> >> I can ping node C from node A and vice versa. In node A, I can
> >> traceroute to node C. The traceroute shows it needs to go through node
> >> B.
> >>
> >> However, when I send packet from node A to node C. Node C does not
> >> receive anything. But if I send packet from node A to node B, node B
> >> can receive that packet.
> >> Not sure what happened. The link shown below is the program I used to
> >> send packet. Both source and destination are MAC address.
> >>
> >> https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/attachments/20111206/52f060cb/attachment.c
> >>
> >> I greatly appreciate any suggestion, comment, and help.
> >>
> >> Thanks
--
Antonio Quartulli
..each of us alone is worth nothing..
Ernesto "Che" Guevara
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-11-28 23:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 4:15 [B.A.T.M.A.N.] batman-adv: Raw Socket Communication liu muye
2012-11-28 5:02 ` Marek Lindner
2012-11-28 23:02 ` liu muye
2012-11-28 23:09 ` liu muye
2012-11-28 23:18 ` Antonio Quartulli [this message]
2012-11-28 23:29 ` liu muye
2012-11-28 23:35 ` Antonio Quartulli
2012-11-28 23:48 ` liu muye
2012-11-28 23:56 ` Antonio Quartulli
2012-11-29 0:02 ` liu muye
2012-11-29 0:05 ` Antonio Quartulli
2012-11-29 0:09 ` liu muye
2012-11-29 2:49 ` liu muye
2012-11-29 3:25 ` Marek Lindner
2012-11-29 3:28 ` Antonio Quartulli
2012-11-29 19:52 ` liu muye
2012-11-29 20:33 ` Sven Eckelmann
2012-11-30 2:41 ` Marek Lindner
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=20121128231824.GE32479@ritirata.org \
--to=ordex@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox