public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Roland Volkmann <roland.volkmann@t-online.de>
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: Wed, 30 Mar 2016 11:09:59 +0200	[thread overview]
Message-ID: <56FB97E7.5050708@t-online.de> (raw)
In-Reply-To: <4506388.qOszBEsOk4@bentobox>

>>> 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). 
>> Let's have a look to the source code. The interesting part is 
>> function "static void batadv_send_outstanding_bcast_packet(struct 
>> work_struct *work)" in file "send.c". There you will find 
> To what are you answering? At least not to my statement.
>> [...] 
> No, it isn't about the incoming or outgoing hard-interfaces. See 
> Marek's reply.

Sorry, that was a misunderstanding. Before Marek's explanation (thank 
you for that) I was read it as comparing incoming to outgoing interface.

>> Here is an updated version of the patch as it is used in current 
>> master branch of gluon matching batman-adv 2016.0: 
> Not sure why you sent some(tm) patch of a patch in this way when there 
> is a guideline how to correctly send them [1]

This was not an official launch of a patch but for information only. 
Neither I myself have a required development environment nor do I like 
to launch Linus' patch as mine. And because of too few knowledge about 
Linux and batman-adv internals, my only contribution can be to show the 
relevance of this issue for Freifunk installations, and looking for 
somebody who can implement the necessary stuff.

Best regards,
Roland.


  reply	other threads:[~2016-03-30  9:09 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 [this message]
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=56FB97E7.5050708@t-online.de \
    --to=roland.volkmann@t-online.de \
    --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