From: "Javier Simó" <javier.simo@urjc.es>
To: Sven Eckelmann <sven@narfation.org>,
Andrei Buciulea <andreibuciulea@gmail.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Fail to create tunnels using br-lan
Date: Fri, 13 Jan 2017 10:59:46 +0100 [thread overview]
Message-ID: <5878A512.9060905@urjc.es> (raw)
In-Reply-To: <8483867.uzBTzBJoDH@bentobox>
Hello Sven
Thanks for your answer, I collaborate with Andrei, who asked the
question, let me try to help to explain, though I suspect that your
message did contain the answer somehow.
We know that batman-adv does multi-hop at L2. That is in fact the
problem. We are trying to test how a network utility called simplemux
may improve the performance in a mesh network using batman-adv. The idea
behind simplemux is that aggregating all packets that node X wants to
sent to node Y at any time, making them share the IP header and
accessing the channel only once for the bundle, can dramatically improve
the performance. Node X should take any packets in the TX queue coming
from different sources and probably going to different destinations but
having the same next hop, and put them together in a bundle. That is
what simplemux does. But actually simplemux operates on a tunnel that
takes the packets sent through a physical interface in X and drives them
to a physical interface of Y.
We don't know well how the tunnel manages the traffic, but possibly the
problem is that it requires the packages coming up from the physical
interface to the IP layer (what does not happen in batman-adv), which is
actually what you say. In this case, may be we cannot do what we wanted
to do :-(
Thanks a lot
Javier
El 13/01/17 a las 08:31, Sven Eckelmann escribió:
> On Donnerstag, 12. Januar 2017 20:27:34 CET Andrei Buciulea wrote:
> [...]
>> *> The tunnels can be successfully created in OpenWRT*I have created the
>> tunnel and assigning the mesh devices an IP(192.168.100.5):
>> The other one mesh device IP is: 192.168.100.4
>>
>> tun0 Link encap:UNSPEC HWaddr
>> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>> inet addr:192.168.100.5 P-t-P:192.168.100.5
>> Mask:255.255.255.0
>> UP POINTOPOINT NOARP MULTICAST MTU:1500 Metric:1
> [...]
>> If anyone has any idea why it does not work I would be very grateful.
> Sorry, but I still don't get what are you doing with layer 3 tunnel stuff and
> what batman-adv has to do with it (it is a layer 2 based protocol which
> requires layer 2 interfaces).
>
> Kind regards,
> Sven
--
---------------------------------------------------
Fco. Javier Simó Reigadas <javier.simo@urjc.es>
Subdirector de Ord. Docente
ETS de Ingeniería de Telecomunicación
D-204, Departamental III
Camino Del Molino, s/n - 28943 Fuenlabrada (Madrid)
Tel: 914888428, Fax: 914887500
Web personal: http://www.tsc.urjc.es/~javier.simo
prev parent reply other threads:[~2017-01-13 9:59 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
[not found] ` <CAEhDGG==nXsChyg6iekEit-TeRKHEte8VrgW_hreaXoX6YN2qg@mail.gmail.com>
2017-01-13 7:31 ` Sven Eckelmann
2017-01-13 9:59 ` Javier Simó [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=5878A512.9060905@urjc.es \
--to=javier.simo@urjc.es \
--cc=andreibuciulea@gmail.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=sven@narfation.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