public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: Carlos Meralto <carlosmeralto@gmail.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] batman-adv: Force line topology
Date: Sat, 13 Jun 2015 21:30:30 +0200	[thread overview]
Message-ID: <1775906.OVcfLHEFNd@sven-edge> (raw)
In-Reply-To: <165699CE-BD67-45D4-AAC1-64663C9B466B@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]

On Saturday 13 June 2015 19:17:57 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.

You have to modify this file or similar ones yourself to avoid that it sets 
IFF_DONT_BRIDGE. And then you have to recompile your kernel with your patch 
and run it - but you should be aware that this is only a hack. It was already 
discussed on this mailing list how the wifi stack avoids that the bridge 
accepts specific types of interfaces [1].

You should also find in this thread a patch [2] which shows how some ebtables 
functionality could in theory also be added to something like batman-adv. You 
should be aware that this is not in the upstream version because it is 
considered not acceptable by the Linux networking subsystem maintainer.

You should also be aware that it is problematic to test to different protocols 
by using two different, protocol/implementation specific ways to force them to 
a specific topologies.

Kind regards,
	Sven

[1] https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2010-May/002718.html
[2] https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2010-May/002731.html

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2015-06-13 19: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
     [not found]   ` <165699CE-BD67-45D4-AAC1-64663C9B466B@gmail.com>
2015-06-13 19:30     ` Sven Eckelmann [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=1775906.OVcfLHEFNd@sven-edge \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=carlosmeralto@gmail.com \
    /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