public inbox for b.a.t.m.a.n@lists.open-mesh.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.] [PATCHv14 5/6] batman-adv: Add IPv4 link-local/IPv6-ll-all-nodes multicast support
Date: Sun, 16 Feb 2014 14:30:38 +0800	[thread overview]
Message-ID: <5422268.oz0seJLFlf@diderot> (raw)
In-Reply-To: <1392482874-9024-6-git-send-email-linus.luessing@web.de>

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

On Saturday 15 February 2014 17:47:53 Linus Lüssing wrote:
> With this patch a node may additionally perform the dropping or
> unicasting behaviour for a link-local IPv4 and link-local-all-nodes
> IPv6 multicast packet, too.
> 
> The extra counter and BATADV_MCAST_WANT_ALL_UNSNOOPABLES flag is needed
> because with a future bridge snooping support integration a node with a
> bridge on top of its soft interface is not able to reliably detect its
> multicast listeners for IPv4 link-local and the IPv6
> link-local-all-nodes addresses anymore (see RFC4541, section 2.1.2.2
> and section 3).
> 
> Even though this new flag does make "no difference" now, it'll ensure
> a seamless integration of multicast bridge support without needing to
> break compatibility later.
> 
> Also note, that even with multicast bridge support it won't be possible
> to optimize 224.0.0.x and ff02::1 towards nodes with bridges, they will
> always receive these ranges.
> 
> Signed-off-by: Linus Lüssing <linus.luessing@web.de>
> ---
>  main.c           |    6 +++
>  main.h           |    1 +
>  multicast.c      |  135
> ++++++++++++++++++++++++++++++++++++++++++++++++++----
> packet.h         |    9 ++++
>  soft-interface.c |    1 +
>  types.h          |   12 +++++
>  6 files changed, 156 insertions(+), 8 deletions(-)

Applied in revision 1c09034.

Thanks,
Marek

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

  reply	other threads:[~2014-02-16  6:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-15 16:47 [B.A.T.M.A.N.] [PATCHv14 0/6] Basic Multicast Optimizations Linus Lüssing
2014-02-15 16:47 ` [B.A.T.M.A.N.] [PATCHv14 1/6] batman-adv: Multicast Listener Announcements via Translation Table Linus Lüssing
2014-02-16  6:23   ` Marek Lindner
2014-02-15 16:47 ` [B.A.T.M.A.N.] [PATCHv14 2/6] batman-adv: introduce capability initialization bitfield Linus Lüssing
2014-02-16  6:24   ` Marek Lindner
2014-02-15 16:47 ` [B.A.T.M.A.N.] [PATCHv14 3/6] batman-adv: Announce new capability via multicast TVLV Linus Lüssing
2014-02-16  6:25   ` Marek Lindner
2014-02-15 16:47 ` [B.A.T.M.A.N.] [PATCHv14 4/6] batman-adv: Modified forwarding behaviour for multicast packets Linus Lüssing
2014-02-16  6:28   ` Marek Lindner
2014-02-15 16:47 ` [B.A.T.M.A.N.] [PATCHv14 5/6] batman-adv: Add IPv4 link-local/IPv6-ll-all-nodes multicast support Linus Lüssing
2014-02-16  6:30   ` Marek Lindner [this message]
2015-06-10  8:52   ` Sven Eckelmann
2014-02-15 16:47 ` [B.A.T.M.A.N.] [PATCHv14 6/6] batman-adv: Send multicast packets to nodes with a WANT_ALL flag Linus Lüssing
2014-02-16  6:32   ` Marek Lindner

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=5422268.oz0seJLFlf@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