From: David Miller <davem@davemloft.net>
To: linus.luessing@c0d3.blue
Cc: yoshfuji@linux-ipv6.org, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org,
linux-wireless@vger.kernel.org, jmorris@namei.org,
linux-kernel@vger.kernel.org, monis@voltaire.com,
kuznet@ms2.inr.ac.ru, kaber@trash.net
Subject: Re: [PATCH net] ipv6: Fix IPv6 packet loss in scenarios involving roaming + snooping switches
Date: Mon, 06 Feb 2017 11:43:29 -0500 (EST) [thread overview]
Message-ID: <20170206.114329.1196570425826508517.davem@davemloft.net> (raw)
In-Reply-To: <20170203071103.25976-1-linus.luessing@c0d3.blue>
From: Linus Lüssing <linus.luessing@c0d3.blue>
Date: Fri, 3 Feb 2017 08:11:03 +0100
> When for instance a mobile Linux device roams from one access point to
> another with both APs sharing the same broadcast domain and a
> multicast snooping switch in between:
>
> 1) (c) <~~~> (AP1) <--[SSW]--> (AP2)
>
> 2) (AP1) <--[SSW]--> (AP2) <~~~> (c)
>
> Then currently IPv6 multicast packets will get lost for (c) until an
> MLD Querier sends its next query message. The packet loss occurs
> because upon roaming the Linux host so far stayed silent regarding
> MLD and the snooping switch will therefore be unaware of the
> multicast topology change for a while.
>
> This patch fixes this by always resending MLD reports when an interface
> change happens, for instance from NO-CARRIER to CARRIER state.
>
> Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>
Looks good to me, applied, thanks.
prev parent reply other threads:[~2017-02-06 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 7:11 [PATCH net] ipv6: Fix IPv6 packet loss in scenarios involving roaming + snooping switches Linus Lüssing
2017-02-06 16:43 ` 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=20170206.114329.1196570425826508517.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bridge@lists.linux-foundation.org \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linus.luessing@c0d3.blue \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=monis@voltaire.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).