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: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] No rebroadcast on mesh links
Date: Tue, 29 Mar 2016 20:55:41 +0200	[thread overview]
Message-ID: <4605306.DPF6tJRphQ@sven-edge> (raw)
In-Reply-To: <20160329175957.GA6539@r2d2.s.lihas.de>

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

On Tuesday 29 March 2016 19:59:57 Adrian Reyer wrote:
[...]
> > It would also be interesting if it should be a simple flag or some if
> > exporting the num_bcasts via $something would be sufficient. Or if the
> > num_bcasts should be split into num_bcasts_otherif and
> > num_bcasts_sameif and then exported.
> 
> It is two different things, the num_bcasts in my understanding is about
> how many times the originator sends out its packets to assume everyone
> has received it.
> The flag we talk about is about if anyone receiving that packet on an
> interface has to send it out on that very interface at all, e.g. it is
> about everyone reachable via that interface sees the same neighbours
> (e.g. switch) or a different group (e.g. wlan adhoc)

Thats why I said that it would have to be split into *sameif and *otherif.

And btw. it is not about the originator. It is handled in 
batadv_send_outstanding_bcast_packet at the same place where you want to have 
the no_rebroadcast check. no_rebroadcast in the patch we are talking [1,2] 
about is currently just ignoring the num_bcasts of a hard-interface for some 
situations (when forw_packet->skb->dev == hard_iface->net_dev).

Kind regards,
	Sven

[1] https://patchwork.open-mesh.org/patch/3434/
[2] https://patchwork.open-mesh.org/patch/4384/

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

  reply	other threads:[~2016-03-29 18:55 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 [this message]
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
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=4605306.DPF6tJRphQ@sven-edge \
    --to=sven@narfation.org \
    --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