linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Knoblauch <knobi@knobisoft.de>
To: linux-net@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, David Stevens <dlstevens@us.ibm.com>
Subject: Re: Any changes in Multicast code between 2.4.20 and 2.4.22/23 ? -> New Info
Date: Wed, 7 Jan 2004 02:27:23 -0800 (PST)	[thread overview]
Message-ID: <20040107102723.67627.qmail@web13910.mail.yahoo.com> (raw)

sorry, wrong subject ...

>
> To rule out further causes, I rebuilt the 2.4.21 version of tg3.o
>(V1.5) for the 2.4.22 kernel (tg3-V1.6). Unfortunatelly the problem
did
>not go away, which point into the direction of the pretty large
>igmp/multicast changes introduced with 2.4.22. Debugging tg3 would
have
>been easier ...

Next tidbit: the problem comes when using a multicast group different
from 224.0.0.1. If I change the group used by Ganglia from 239.2.11.71
to 224.0.0.1 all of a sudden the multicasts come in.

Hope this helps the specialists to track it down.

Martin


=====
------------------------------------------------------
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www:   http://www.knobisoft.de

             reply	other threads:[~2004-01-07 10:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07 10:27 Martin Knoblauch [this message]
     [not found] <OFF9934921.DF9DB0E3-ON88256E15.00658D89@us.ibm.com>
2004-01-09  8:37 ` Any changes in Multicast code between 2.4.20 and 2.4.22/23 ? -> New Info Martin Knoblauch
     [not found] <OFFB53E1E3.C0B1F8BC-ON88256E14.003560C9@us.ibm.com>
2004-01-07 14:08 ` Martin Knoblauch
2004-01-08 18:03 ` Martin Knoblauch
     [not found] <OFDDD008B9.906B9BD6-ON88256E14.0038B2E4@us.ibm.com>
2004-01-07 19:24 ` Martin Knoblauch
  -- strict thread matches above, loose matches on Subject: below --
2004-01-07  9:28 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=20040107102723.67627.qmail@web13910.mail.yahoo.com \
    --to=knobi@knobisoft.de \
    --cc=dlstevens@us.ibm.com \
    --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;
as well as URLs for NNTP newsgroup(s).