b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH v5 0/2] batman-adv: Add routable multicast optimizations
Date: Fri, 14 Jun 2019 20:37:09 +0200	[thread overview]
Message-ID: <2692232.m69ynxnPBa@sven-edge> (raw)
In-Reply-To: <20190611205841.5841-1-linus.luessing@c0d3.blue>

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

On Tuesday, 11 June 2019 22:58:39 CEST Linus Lüssing wrote:
> The following patchset fills the next gaps in the multicast address
> rules page by adding support for group-aware optimizations for
> multicast addresses of scope greater than link-local. So far, only
> link-local addresses were optimized as packets with routable
> addresses not only need to be forwarded to local multicast listeners
> but also multicast routers.

Applied. But please don't forget about the missing changes in the related 
tools:

* https://www.open-mesh.org/issues/390
* https://www.open-mesh.org/issues/391
* https://www.open-mesh.org/issues/392

Kind regards,	
	Sven

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

  parent reply	other threads:[~2019-06-14 18:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 20:58 [PATCH v5 0/2] batman-adv: Add routable multicast optimizations Linus Lüssing
2019-06-11 20:58 ` [PATCH v5 1/2] batman-adv: mcast: detect, distribute and maintain multicast router presence Linus Lüssing
2019-06-11 20:58 ` [PATCH v5 2/2] batman-adv: mcast: apply optimizations for routable packets, too Linus Lüssing
2019-06-14 18:37 ` Sven Eckelmann [this message]
2019-06-23  8:05   ` [PATCH v5 0/2] batman-adv: Add routable multicast optimizations Sven Eckelmann

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=2692232.m69ynxnPBa@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;
as well as URLs for NNTP newsgroup(s).