From: Antonio Quartulli <a@unstable.cc>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<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: Mon, 19 Dec 2016 18:10:24 +0800 [thread overview]
Message-ID: <20161219101024.GB8485@prodigo.lan> (raw)
In-Reply-To: <CAPkwMUejbf31RfVY_nCJSVwe=_mGVO3y5PY9zzfkQk0eDc1HTA@mail.gmail.com>
On Mon, Dec 19, 2016 at 11:06:01AM +0100, Carlos Rey-Moreno wrote:
> Hi everyone,
>
> A student who is collaborating with me, Andrei, cc'ed, is carrying out
> traffic performance analysis in a mesh network (which uses batman-adv)
> in order to compare the benefits of introducing Simplemux [1].
> Basically, simplemux multiplexes small packets in bigger packets and
> compresses them to reduce overhead. These packets are then sent
> through a tunnel to another end in the network.
>
> So far, simplemux shows very positive results by creating the tunnel
> in between two computers connected at each end of a multihop network
> composed by a chain of 5 nodes.
>
> The idea would be to test the performance benefits of simplemux when
> the tunnels are created between the mesh nodes instead, so they could
> aggregate, let's say, all the VoIP packets from different SIP clients
> calling other SIP clients in the mesh or via the gateway.
>
> 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, i.e. eth0, but fails with br-lan
> provided it is a virtual interface.
>
> # openvpn --mktun --dev tun0 --user root
>
> # ifconfig tun0 up
>
> # ./simplemux -i tun0 -e br-lan -M N -c 192.168.0.5
>
> I was wondering if anyone in the list could point Andrei in the right direction.
>
> Thank you very much in advance.
Dear Carlos,
this looks pretty much about OpenVPN (if I am not wrong). Are you sure you
posted it to the right mailing list?
Cheers,
--
Antonio Quartulli
next prev parent reply other threads:[~2016-12-19 10:10 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 [this message]
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ó
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=20161219101024.GB8485@prodigo.lan \
--to=a@unstable.cc \
--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