From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] No rebroadcast on mesh links
Date: Thu, 31 Mar 2016 18:53:24 +0200 [thread overview]
Message-ID: <20160331165324.GC2989@otheros> (raw)
In-Reply-To: <20160331154931.GE5258@prodigo.lan>
On Thu, Mar 31, 2016 at 11:49:31PM +0800, Antonio Quartulli wrote:
> On Thu, Mar 31, 2016 at 05:35:13PM +0200, Linus Lüssing wrote:
> > On Thu, Mar 31, 2016 at 02:11:19PM +0200, Simon Wunderlich wrote:
> > - can still break some setups if bridges on remote devices are involved
> > (for instance bridge between ethernet and adhoc, like Adrian
> > pointed out)
>
> in this case the user can still manually change the flag through sysfs no ?
Hm, depends. The owner of that new device with the bridge
cannot necessarilly change the config on the batman-adv node as
that can be a totally different device with another owner.
Additionally the broken setups might be difficult to debug or even
notice.
next prev parent reply other threads:[~2016-03-31 16:53 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 21:35 [B.A.T.M.A.N.] No rebroadcast on mesh links Roland Volkmann
2016-03-25 22:46 ` Sven Eckelmann
2016-03-25 23:19 ` Roland Volkmann
2016-03-27 2:38 ` Marek Lindner
2016-03-28 13:43 ` Roland Volkmann
2016-03-28 14:43 ` Marek Lindner
2016-03-28 19:11 ` Linus Lüssing
2016-03-28 21:19 ` Roland Volkmann
2016-03-28 23:52 ` Linus Lüssing
2016-03-29 8:37 ` Adrian Reyer
2016-03-29 9:50 ` Sven Eckelmann
2016-03-29 17:59 ` Adrian Reyer
2016-03-29 18:55 ` Sven Eckelmann
2016-03-29 23:37 ` Roland Volkmann
2016-03-30 2:15 ` Marek Lindner
2016-03-30 8:00 ` Sven Eckelmann
2016-03-30 9:09 ` Roland Volkmann
2016-03-30 12:23 ` Sven Eckelmann
2016-03-30 11:58 ` Simon Wunderlich
2016-03-30 13:58 ` Adrian Reyer
2016-03-30 16:08 ` Sven Eckelmann
2016-03-30 19:55 ` Adrian Reyer
2016-03-31 12:11 ` Simon Wunderlich
2016-03-31 12:21 ` Simon Wunderlich
2016-03-31 15:54 ` Antonio Quartulli
2016-03-31 16:25 ` Linus Lüssing
2016-03-31 15:35 ` Linus Lüssing
2016-03-31 15:49 ` Antonio Quartulli
2016-03-31 16:53 ` Linus Lüssing [this message]
2016-03-31 16:01 ` Antonio Quartulli
2016-03-31 17:17 ` Linus Lüssing
2016-04-13 12:17 ` Simon Wunderlich
2016-04-13 12:22 ` Sven Eckelmann
2016-03-29 0:02 ` Linus Lüssing
2016-03-29 6:38 ` Roland Volkmann
2016-03-30 8:08 ` Simon Wunderlich
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=20160331165324.GC2989@otheros \
--to=linus.luessing@c0d3.blue \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.