Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: redmcg@redmandi.dyndns.org
Cc: kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ipv6: icmp6: Allow icmp messages to be looped back
Date: Sat, 16 Dec 2017 22:52:12 -0500 (EST)	[thread overview]
Message-ID: <20171216.225212.1791534849895795249.davem@davemloft.net> (raw)
In-Reply-To: <1513163697-21136-1-git-send-email-redmcg@redmandi.dyndns.org>

From: Brendan McGrath <redmcg@redmandi.dyndns.org>
Date: Wed, 13 Dec 2017 22:14:57 +1100

> One example of when an ICMPv6 packet is required to be looped back is
> when a host acts as both a Multicast Listener and a Multicast Router.
> 
> A Multicast Router will listen on address ff02::16 for MLDv2 messages.
> 
> Currently, MLDv2 messages originating from a Multicast Listener running
> on the same host as the Multicast Router are not being delivered to the
> Multicast Router. This is due to dst.input being assigned the default
> value of dst_discard.
> 
> This results in the packet being looped back but discarded before being
> delivered to the Multicast Router.
> 
> This patch sets dst.input to ip6_input to ensure a looped back packet
> is delivered to the Multicast Router.
> 
> Signed-off-by: Brendan McGrath <redmcg@redmandi.dyndns.org>

Ok, after a lot of consideration this seems like a reasonable way to
solve this problem.

Applied, thank you.

      reply	other threads:[~2017-12-17  3:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 11:14 [PATCH] ipv6: icmp6: Allow icmp messages to be looped back Brendan McGrath
2017-12-17  3:52 ` David Miller [this message]

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=20171216.225212.1791534849895795249.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=redmcg@redmandi.dyndns.org \
    --cc=yoshfuji@linux-ipv6.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