public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Gui Iribarren <gui@altermundi.net>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] batman-adv: Force line topology
Date: Sun, 14 Jun 2015 11:30:23 -0300	[thread overview]
Message-ID: <557D8FFF.4070601@altermundi.net> (raw)
In-Reply-To: <CALaFpeV2DNt9a8--P+CP2_=1fhHkMWJ2+4H6dMDqYAq0scpA0g@mail.gmail.com>

On 13/06/15 15:15, Carlos Meralto wrote:
> Thanks for the answer Sven.
> 
> You can patch the driver to allow this (it is just a simple check which
> disallows it in most drivers... or actually in wireless core [1]). But you
> should make sure that you still use the same mac addresses for vif + bridge
> and don't end up with 4 address packets.
> 
> 
> Can you explain how I can apply this "patch”? I saw the file attached
> but i don't know what parameters must change.
> 
> There is already a way to force a topology in batman-adv?
> 
> 
> No. There were only different solutions (not acceptable for the linux kernel)
> which did this directly in batman-adv. A very prominent (and easy to find)
> solution was from Martin [2]
> 
> The idea behind batman-adv is that it finds paths and thus automatically
> creates a good virtual topologies.
> 
> 
> If you can not use ebtables I will try to use the patch that Martin did.
> 
> I'm blocked with no solution.
> 
> Thanks in advance.
> 
> 
> I don't know why you want to use wlan and you also don't explain it in your
> mail. You could for example also use emulation + vde2 [3] since you already
> try to emulate a setup which is not there in reality.
> 
> 
> The first task of my thesis is to make a comparison between
> open802.11s and batman-adv for node discovery time and througput, in
> function of hops and recovery in case of failure. So i want make this
> tests in a real scenario...

then make it a real scenario :)

the simulated line topology will not behave the same as a real-world
line topology in terms of throughput, due to interferences that will
happen in your simulated scenario, that wouldn't happen in real life

if you still want to try it, an alternative (to patching batman-adv) is
to use VLANs on top of the adhoc interfaces
so instead of adding plain adhoc0 with "batctl if"
first create some vlans over adhoc0
say, on first node, create and add adhoc0.1 to batman
then on second node, create adhoc0.1 and adhoc0.2 then add both
interfaces to batman,
on third node, adhoc0.2 and adhoc0.3... and so on
this way, the third node will have no links with the first node.
it won't help with the interference problem i mentioned above, tho.

good luck!

> 
> Thanks in advance.
> 
> Best Regards,
> Carlos Meralto
> 

  reply	other threads:[~2015-06-14 14:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12 12:31 [B.A.T.M.A.N.] batman-adv: Force line topology Carlos Meralto
2015-06-13 13:58 ` Sven Eckelmann
2015-06-13 18:15   ` Carlos Meralto
2015-06-14 14:30     ` Gui Iribarren [this message]
     [not found]   ` <165699CE-BD67-45D4-AAC1-64663C9B466B@gmail.com>
2015-06-13 19:30     ` Sven Eckelmann

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=557D8FFF.4070601@altermundi.net \
    --to=gui@altermundi.net \
    --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