From: Marek Lindner <mareklindner@neomailbox.ch>
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.] [PATCH] batman-adv: introduce 'no_rebroadcast' option
Date: Wed, 25 Sep 2013 23:03:48 +0800 [thread overview]
Message-ID: <1680806.MqrY0WE4J8@diderot> (raw)
In-Reply-To: <20130924145723.GN18530@Linus-Debian>
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
On Tuesday 24 September 2013 16:57:24 Linus Lüssing wrote:
> On Tue, Sep 24, 2013 at 03:46:50PM +0200, Antonio Quartulli wrote:
> > On Tue, Sep 24, 2013 at 03:40:33PM +0200, Linus Lüssing wrote:
> > >
> > >
> > > Using this option wrongly will break your mesh network, use this option
> > > wisely and at your own risk!
> >
> >
> >
> > Exactly for this reason (As we discussed on IRC) I think this mechanism
> > should be reasoned a bit more.
>
> Hm, my personal reason to want such a feature is included, the VPN
> example. And since I know that using batman-adv over VPNs is not
> uncommon, I'd love to have this feature upstream.
Admittedly, I haven't followed the entire discussion but what speaks against
setting the rebroadcast count define for non-wireless to 0 ? Matthias (if I am
not mistaken) provided a patch for the wireless / non-wireless distinction not
too long ago.
Seems way easier as we are looking for a quick and temporary solution ?
Cheers,
Marek
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-09-25 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 13:40 [B.A.T.M.A.N.] [PATCH] batman-adv: introduce 'no_rebroadcast' option Linus Lüssing
2013-09-24 13:46 ` Antonio Quartulli
2013-09-24 14:57 ` Linus Lüssing
2013-09-25 15:03 ` Marek Lindner [this message]
2013-10-20 9:21 ` Linus Lüssing
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=1680806.MqrY0WE4J8@diderot \
--to=mareklindner@neomailbox.ch \
--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