From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: "Francisco Javier Simó Reigadas" <javier.simo@urjc.es>,
"Andrei Buciulea" <andreibuciulea@gmail.com>
Subject: Re: [B.A.T.M.A.N.] Fail to create tunnels using br-lan
Date: Thu, 05 Jan 2017 08:51:02 +0100 [thread overview]
Message-ID: <2739485.ZOxij8zM53@bentobox> (raw)
In-Reply-To: <CAPkwMUfc9K3J+0wwegZOuLCba5JY_5GP33jcykPa1etpWKkNsw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
On Montag, 19. Dezember 2016 11:55:40 CET Carlos Rey-Moreno wrote:
> Dear Antonio, we will post it in the OpenVPN mailing list too, but I
> was hoping that someone in the list had been able to establish tunnels
> in between batmand-adv nodes using the br-lan interface.
Sorry, but we don't understand what your question has to do with batman-adv.
In your example there is no actual reference to batman-adv. Only simplemux and
OpenVPN is shown in the example. We don't know simplemux and cannot tell you
why it may not work (is it the problematic tool? Not really clear in your
question). The latter is known but seems to be used in L3 mode and therefore
useless for bridges and batman-adv.
> The tunnels can be successfully created in OpenWRT, but it fails when
> assigning the physical interface the tunnel should use. It works when
> a physical interface is used,
So it fails and works at the same time with "physical interface"s? What
exactly fails here? Is it batman-adv related? Doesn't look to me like it does.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-01-05 7:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 10:06 [B.A.T.M.A.N.] Fail to create tunnels using br-lan Carlos Rey-Moreno
2016-12-19 10:10 ` Antonio Quartulli
2016-12-19 10:55 ` Carlos Rey-Moreno
2017-01-05 7:51 ` Sven Eckelmann [this message]
[not found] ` <CAEhDGG==nXsChyg6iekEit-TeRKHEte8VrgW_hreaXoX6YN2qg@mail.gmail.com>
2017-01-13 7:31 ` Sven Eckelmann
2017-01-13 9:59 ` Javier Simó
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=2739485.ZOxij8zM53@bentobox \
--to=sven@narfation.org \
--cc=andreibuciulea@gmail.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=javier.simo@urjc.es \
/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