From: "David S. Miller" <davem@redhat.com>
To: dlstevens@us.ibm.com
Cc: netdev@oss.sgi.com, stevenh@xsmail.com
Subject: Re: multicast loop with include filters fix [PATCH]
Date: Thu, 22 Jan 2004 17:57:05 -0800 (PST) [thread overview]
Message-ID: <20040122.175705.71096838.davem@redhat.com> (raw)
In-Reply-To: <OF56B39506.D81AEE48-ON88256E24.000A2D7B@us.ibm.com>
From: David Stevens <dlstevens@us.ibm.com>
Date: Thu, 22 Jan 2004 19:02:07 -0700
When sending a multicast and using looping back a copy to the
local machine, the interface filter checks can be done before the
source address is specified. For an INCLUDE filter, this won't match
the allowed sources and the packets won't be delivered locally,
even when the ultimate source address chosen is in the allowed list.
The patch below fixes the filter checks for both IGMPv3 and MLDv2
to only apply when a source address is available.
Looks good, I guess a 2.4.x variant is forthcoming?
Thanks.
next prev parent reply other threads:[~2004-01-23 1:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 2:02 multicast loop with include filters fix [PATCH] David Stevens
2004-01-23 1:57 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-23 20:27 David Stevens
2004-01-23 22:39 David Stevens
2004-01-24 18:00 ` David S. 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=20040122.175705.71096838.davem@redhat.com \
--to=davem@redhat.com \
--cc=dlstevens@us.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=stevenh@xsmail.com \
/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).