From: Lawrence MacIntyre <lpz@ornl.gov>
To: knobi@knobisoft.de
Cc: David Stevens <dlstevens@us.ibm.com>,
linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Any changes in Multicast code between 2.4.20 and 2.4.22/23 ?
Date: Tue, 06 Jan 2004 07:59:07 -0500 [thread overview]
Message-ID: <1073393946.5626.7.camel@nautique> (raw)
In-Reply-To: <20040106022122.11388.qmail@web13906.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 2815 bytes --]
Can you look on the adjacent multicast router(s) and see if your host is
listed as a group member? Or is this done with just a flat IP network
(one subnet)?
On Mon, 2004-01-05 at 21:21, Martin Knoblauch wrote:
> --- David Stevens <dlstevens@us.ibm.com> wrote:
> >
> >
> Hi David,
>
> >
> >
> > Martin,
> > If you have other hosts on that network that have sent IGMP
> > reports,
> > then
> > the reporter flag will be cleared-- only one member on a network
> > needs to
> > send
> > reports. That doesn't prevent the host from receiving multicasts--
> > presence
> > in
> > /proc/net/igmp indicates it did join the group.
>
> OK. I just wondered, because all hosts running the 2.4.20-18.7smp
> kernel (RH7.3 errata) show the "1" in the reporter field, while all
> hosts running 2.4.22/2.4.23 (vanilla plus NFS fixes from Trond) show
> "0".
>
> > Please send me some details about your set-up and I may be able
> > to
> > help.
>
> We are running 21 HP/DL380G3.Each has two internal Broadcom NICs. The
> second one (eth1) is used for the Ganglia multicast.
>
> The kernels are 2.4.22 and 2.4.23 (now .24) with some NFS patches. In
> the case of 2.4.24 those are:
>
> 01-posix_race
> 02-fix_commit
> 03-fix_osx
> 04-fix_lockd3
> 06-fix_unlink
> 07_seekdir
>
> from http://www.fys.uio.no/~trondmy/src/Linux-2.4.x/2.4.23-rc1 None of
> those looks like it does something to multicasts. In the worst case I
> could try to run with plain 2.4.22/23, but that would have to ait until
> Wednesday.
>
> The kernel-config file is included.
>
> > First, are the sender and receiver on the same network, or are
> > you
> > using a multicast router?
>
> No. All systems are on the same network.
>
> > Second, can you send me a tcpdump-format packet trace
> > (preferrably
> > only the multicast traffic, and as small as you can make it)?
>
> What exactely do you want to see? On which box should I run tcpdump?
> Which options (I'm not that deep into network debugging :-)?
>
>
> > You mentioned tg3-- have you tried this with other hardware
> > that
> > worked?
> >
>
> The tg3 works with the 2.4.20-18.7smp (and earlier) kernels. It just
> does not work with 2.4.22/23 (did not check 2.4.21).
>
> Unfortunatelly I have no other boxes to test with. I only can say that
> Ganglia never failed in this particular way on any setup.
>
> Thanks
> Martin
>
> =====
> ------------------------------------------------------
> Martin Knoblauch
> email: k n o b i AT knobisoft DOT de
> www: http://www.knobisoft.de
--
Lawrence MacIntyre 865.574.8696 lpz@ornl.gov
Oak Ridge National Laboratory
High Performance Information Infrastructure Technology Group
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-06 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF82F2C5E5.10FE707F-ON88256E12.00701FFA@us.ibm.com>
2004-01-06 2:21 ` Any changes in Multicast code between 2.4.20 and 2.4.22/23 ? Martin Knoblauch
2004-01-06 12:59 ` Lawrence MacIntyre [this message]
2004-01-06 13:17 Martin Knoblauch
-- strict thread matches above, loose matches on Subject: below --
2004-01-06 11:11 Martin Knoblauch
2004-01-05 15:02 Martin Knoblauch
2004-01-05 10:39 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=1073393946.5626.7.camel@nautique \
--to=lpz@ornl.gov \
--cc=dlstevens@us.ibm.com \
--cc=knobi@knobisoft.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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