From: James Morris <jmorris@intercode.com.au>
To: Niels den Otter <otter@surfnet.nl>
Cc: Brian Litzinger <brian@top.worldcontrol.com>,
"David S. Miller" <davem@redhat.com>, <kuznet@ms2.inr.ac.ru>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH] Re: Booting 2.5.63 vs 2.4.20 I can't read multicast data
Date: Thu, 6 Mar 2003 16:06:46 +1100 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0303061605001.27962-100000@blackbird.intercode.com.au> (raw)
In-Reply-To: <20030304223953.GA3114@pangsit>
On Tue, 4 Mar 2003, Niels den Otter wrote:
> You appear to be strugling with the same problem I have. What I find is
> that the multicast application binds to the loopback instead of ethernet
> interface (also no IGMP joins are send out on the ethernet interface).
Please try the patch below.
- James
--
James Morris
<jmorris@intercode.com.au>
diff -urN -X dontdiff linux-2.5.64.orig/net/ipv4/igmp.c linux-2.5.64.w1/net/ipv4/igmp.c
--- linux-2.5.64.orig/net/ipv4/igmp.c Tue Feb 25 15:03:26 2003
+++ linux-2.5.64.w1/net/ipv4/igmp.c Thu Mar 6 15:55:37 2003
@@ -606,7 +606,7 @@
static struct in_device * ip_mc_find_dev(struct ip_mreqn *imr)
{
struct flowi fl = { .nl_u = { .ip4_u =
- { .daddr = imr->imr_address.s_addr } } };
+ { .daddr = imr->imr_multiaddr.s_addr } } };
struct rtable *rt;
struct net_device *dev = NULL;
struct in_device *idev = NULL;
next prev parent reply other threads:[~2003-03-06 4:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 7:39 brian
2003-03-04 22:39 ` Niels den Otter
2003-03-05 6:11 ` Booting 2.5.63 vs 2.4.20 I can " brian
2003-03-05 8:25 ` Niels den Otter
2003-03-06 9:49 ` brian
2003-03-06 5:06 ` James Morris [this message]
2003-03-06 4:51 ` [PATCH] Re: Booting 2.5.63 vs 2.4.20 I can't " David S. Miller
2003-03-06 9:48 ` Niels den Otter
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=Pine.LNX.4.44.0303061605001.27962-100000@blackbird.intercode.com.au \
--to=jmorris@intercode.com.au \
--cc=brian@top.worldcontrol.com \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=otter@surfnet.nl \
/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
all inboxes | Powered by JetHome®