From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: David Lamparter <equinox@diac24.net>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
Stephen Hemminger <stephen@networkplumber.org>,
Nicolas Dichtel <nicolas.dichtel@6wind.com>
Subject: Re: [PATCH 1/2] ipv6: addrconf: fix mcast route for GRE devices
Date: Fri, 01 Aug 2014 00:05:25 +0200 [thread overview]
Message-ID: <1406844325.13603.16.camel@localhost> (raw)
In-Reply-To: <1406840034-140848-2-git-send-email-equinox@diac24.net>
Hi David,
Next time please also specify which tree you want this patch applied to.
We use [PATCH net] for patches which should go into the rc2+ and [PATCH
net-next] for rc1. Thanks!
On Do, 2014-07-31 at 22:53 +0200, David Lamparter wrote:
> GRE devices, for some reason, were coming up with an autoconfigured
> address, but no ff00::/8 route in the local table. This breaks any kind
> of multicast, in particular OSPFv3, mDNS, - and ND. In fact, IPv6 only
> works at all because there is little need for ND on PtP devices.
>
> Adding any other IPv6 address on the device from userspace would rectify
> this issue through inet6_addr_add()/addrconf_add_dev() - and would leave
> the route around even if the address was later removed. (This is
> probably why this issue was not discovered earlier. AFAICS it has been
> there from the beginning, e.g. aee80b5 "generate link local address for
> GRE tunnel")
>
> (Note: multicast is supported on GRE devices of all kinds, including PtP
> GRE, P-t-Mcast GRE and NBMA-GRE.)
>
> Fixes: aee80b54b235 (ipv6: generate link local address for GRE tunnel)
> Signed-off-by: David Lamparter <equinox@diac24.net>
> Cc: Hannes Frederic Sowa <hannes@stressinduktion.org>
> Cc: Stephen Hemminger <stephen@networkplumber.org>
> Cc: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Acked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Dave, it would make sense to queue this up for net and stable (or only
net-next if there is no merge before the release).
Thanks,
Hannes
next prev parent reply other threads:[~2014-07-31 22:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 0:55 [PATCH net-next] ipv6: addrconf: fix mcast route for GRE devices David Lamparter
2014-07-30 15:14 ` Hannes Frederic Sowa
2014-07-30 15:35 ` David Lamparter
2014-07-30 15:39 ` [PATCH v2] " David Lamparter
2014-07-31 19:06 ` David Miller
2014-07-31 19:37 ` Hannes Frederic Sowa
2014-07-31 20:19 ` David Lamparter
2014-07-31 20:53 ` [PATCH v3] " David Lamparter
2014-07-31 20:53 ` [PATCH 1/2] " David Lamparter
2014-07-31 22:05 ` Hannes Frederic Sowa [this message]
2014-07-31 20:53 ` [PATCH 2/2] ipv6: addrconf: clean up device type handling David Lamparter
2014-07-31 22:13 ` Hannes Frederic Sowa
2014-08-01 5:31 ` David Miller
2014-07-30 15:58 ` [RFC alternate] " David Lamparter
2014-07-30 16:12 ` Hannes Frederic Sowa
2014-07-30 16:23 ` David Lamparter
2014-07-30 16:44 ` Hannes Frederic Sowa
2014-07-31 9:27 ` Hannes Frederic Sowa
2014-07-30 16:09 ` [PATCH net-next] ipv6: addrconf: fix mcast route for GRE devices Hannes Frederic Sowa
2014-07-30 16:31 ` David Lamparter
2014-07-30 16:52 ` Hannes Frederic Sowa
2014-07-30 17:35 ` David Lamparter
2014-07-30 18:03 ` Hannes Frederic Sowa
2014-07-30 18:20 ` Dan Williams
2014-07-31 19:06 ` David Miller
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=1406844325.13603.16.camel@localhost \
--to=hannes@stressinduktion.org \
--cc=davem@davemloft.net \
--cc=equinox@diac24.net \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=stephen@networkplumber.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).