From: Martin Knoblauch <knobi@knobisoft.de>
To: Frank Lind <flind@haystack.mit.edu>, linux-kernel@vger.kernel.org
Cc: knobi@knobisoft.de
Subject: Re: Multicast problems between 2.4.20 and 2.4.21?
Date: Tue, 25 May 2004 02:49:33 -0700 (PDT) [thread overview]
Message-ID: <20040525094933.37642.qmail@web13906.mail.yahoo.com> (raw)
In-Reply-To: <40B25CFA.3000105@haystack.mit.edu>
--- Frank Lind <flind@haystack.mit.edu> wrote:
> Hi,
>
> Was there ever a resolution to the multicast issues with kernels
> beyond
> 2.4.20?
>
Hi Frank,
no real resolution in my case, just a gross hack :-) With help from
some network folks and a lot of experiments we found out that somehow
IGMPv3 did cause the problems. The new protocol was introduced in
2.4.20 or 2.4.21.
The problem only shows up when using MC groups different from
224.0.0.1. Assuming the correctness of the IGMPv3 code, the suspects
were the switch (some CISCO 6000, with the latest - v3 capable-
Firmware) or the network card (tg3). *I* am almost sure it is not the
card. Exchanging the driver from a "working" kernel into the new kernel
(and vice versa) did not change anything. The new kernel did not work
with the old driver, and the old kernel worked fine with the new
driver. So it is likely the switch.
Solution for me was to force IGMPv2 instead of v3. The patch for taht
looks like:
--- ../../../linux-2.4.23/net/ipv4/igmp.c Fri Nov 28 19:26:21
2003
+++ ./igmp.c Fri Jan 9 16:59:21 2004
@@ -124,8 +124,13 @@
#define IGMP_V1_SEEN(in_dev) ((in_dev)->mr_v1_seen && \
time_before(jiffies, (in_dev)->mr_v1_seen))
+#if 0
#define IGMP_V2_SEEN(in_dev) ((in_dev)->mr_v2_seen && \
time_before(jiffies, (in_dev)->mr_v2_seen))
+#else
+#define IGMP_V2_SEEN(in_dev) (1)
+#endif
+
The same problem occured on another cluster (again tg3 cards - maybe
there is something ...) and an HP/Procurve-41xx switch. Here we just
switched to using 224.0.0.1 to solve the problem (we could not reboot
to use a patched kernel).
B^hCheers
Martin
=====
------------------------------------------------------
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www: http://www.knobisoft.de
next prev parent reply other threads:[~2004-05-25 9:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 20:37 Frank Lind
2004-05-25 9:49 ` Martin Knoblauch [this message]
2004-05-25 17:38 ` David S. Miller
2004-05-25 18:15 ` Martin Knoblauch
2004-05-25 18:18 ` Frank Lind
2004-05-25 19:59 ` David S. Miller
2004-05-25 20:14 ` Martin Knoblauch
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=20040525094933.37642.qmail@web13906.mail.yahoo.com \
--to=knobi@knobisoft.de \
--cc=flind@haystack.mit.edu \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®