All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Lindner <mareklindner@neomailbox.ch>
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 10:15:30 +0800	[thread overview]
Message-ID: <2039668.yJixVeb7rD@voltaire> (raw)
In-Reply-To: <56FB11B7.10103@t-online.de>

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

On Wednesday, March 30, 2016 01:37:27 Roland Volkmann wrote:
> 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
> 
>      soft_iface = forw_packet->if_incoming->soft_iface;
> [...]
>      /* rebroadcast packet */
>      rcu_read_lock();
>      list_for_each_entry_rcu(hard_iface, &batadv_hardif_list, list) {
>          if (hard_iface->soft_iface != soft_iface)   /* !!! */
>              continue;
> 
>          if (forw_packet->num_packets >= hard_iface->num_bcasts)
>              continue;
> 
> The if-Statement marked with /* !!! */ results in "true", if 
> incoming-interface isn't identical to outgoing-interface. Because the 
> patch is included after this line, it is relevant for resending 
> broadcasts to the incoming interface only.

There seems to be a misunderstanding. With soft-interfaces batman-adv refers 
to the logic interface created for each mesh (often: bat0, bat1, etc). 
Consequently, the '!!!' marked if statement checks whether or not a given 
hard-interface (read: wlan0, eth0, etc) belongs to the same soft-interface the 
to be forwarded packet belongs to.

Hope that helps!

Cheers,
Marek

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

  reply	other threads:[~2016-03-30  2:15 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 [this message]
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=2039668.yJixVeb7rD@voltaire \
    --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 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.