From: Andreas Pape <APape@phoenixcontact.com>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: [B.A.T.M.A.N.] Antwort: Re: Antwort: Re: Question concerning batman-adv bug #173 "Mesh packets on bat0"
Date: Wed, 18 Feb 2015 15:56:47 +0100 [thread overview]
Message-ID: <OFDE6F3C6C.B8D7D72A-ONC1257DF0.0050412D-C1257DF0.00521AC2@phoenixcontact.com> (raw)
In-Reply-To: <6979890.dWcEGHjvn6@voltaire>
>At this point the mesh is working to your expectation ? Can you transport
>payload across the mesh ? If so, this is a deviation from #173 - wouldn't
you
>agree ?
Before adding bat0 to the bridge br0 I can communicate via the mesh
interface. I configured ip addresses for the bat0 interfaces on my devices
and the ping worked without problems. But I understood from #173 that
pinging was possible in that case, too. I'm referring to #173 because I
can see the ogm messages received via wlan also at the bat0 interface,
which was not the case in 2013.1.0 and earlier - if I remember my tests
correctly...
In the meantime I found out that not only batman-adv stops receiving the
ogm messages at ath0 but also the wpa_supplicant does not receive EAPOL
frames any more as soon as bat0 is attached to the bridge br0 if I try to
use WPA with the mesh interface (wpa_supplicant -i ath0). But I can see
the EAPOL frames at the bridge interface br0 (via batctl td br0). Strange.
I'll come back to you as soon as I have tested your latest patches.
Thanks for your support,
Andreas
next prev parent reply other threads:[~2015-02-18 14:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 7:35 [B.A.T.M.A.N.] Question concerning batman-adv bug #173 "Mesh packets on bat0" Andreas Pape
2015-02-18 11:26 ` Marek Lindner
2015-02-18 12:28 ` [B.A.T.M.A.N.] Antwort: " Andreas Pape
2015-02-18 13:55 ` Marek Lindner
2015-02-18 14:56 ` Andreas Pape [this message]
2015-02-18 15:22 ` [B.A.T.M.A.N.] Antwort: Antwort: " Andreas Pape
2015-02-18 15:45 ` Marek Lindner
2015-02-18 16:10 ` [B.A.T.M.A.N.] Antwort: " Andreas Pape
2015-02-19 4:15 ` Marek Lindner
2015-02-19 8:31 ` Andreas Pape
2015-02-19 9:40 ` Marek Lindner
2015-02-19 10:28 ` [B.A.T.M.A.N.] Antwort: " Andreas Pape
2015-02-19 10:36 ` 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=OFDE6F3C6C.B8D7D72A-ONC1257DF0.0050412D-C1257DF0.00521AC2@phoenixcontact.com \
--to=apape@phoenixcontact.com \
--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;
as well as URLs for NNTP newsgroup(s).