public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Antonio Quartulli <antonio@meshcoding.com>
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: Tue, 24 Sep 2013 15:46:50 +0200	[thread overview]
Message-ID: <20130924134650.GP3911@neomailbox.net> (raw)
In-Reply-To: <1380030033-11533-1-git-send-email-linus.luessing@web.de>

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

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. As I told you, it would be nice to have a self-activating
mechanism which is able to switch it on or off when really needed.

The common network administrator will probably not have enough knowledge to
understand when this is useful or when this is breaking things.


Moreover, with this patch you are adding a userspace API that we won't be able
to remove anymore (!) and since the feature needs some more time before being
mature I'd rather to suggest to avoid this.


Cheers,

-- 
Antonio Quartulli

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-09-24 13:46 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 [this message]
2013-09-24 14:57   ` Linus Lüssing
2013-09-25 15:03     ` Marek Lindner
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=20130924134650.GP3911@neomailbox.net \
    --to=antonio@meshcoding.com \
    --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