The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Martin Knoblauch <knobi@knobisoft.de>
To: linux-net@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Any changes in Multicast code between 2.4.20 and 2.4.22/23 ?
Date: Mon, 5 Jan 2004 07:02:52 -0800 (PST)	[thread overview]
Message-ID: <20040105150252.13443.qmail@web13904.mail.yahoo.com> (raw)

>Hi,
>
>besides wishing everybody a Happy new Year 2004, I have one question.
>Have there been any changes in the multicast handling between 2.4.20
>and 2.4.22/23? Maybe specific to the "tg3" driver?
>
>Reason for my question is that the Ganglia monitoring toolkit stopped
>working with 2.4.22/23 kernels. Apparently mulicatst get sent, but
>nothing is received.
>
>Any ideas?
>
>
>Thanks
>Martin

Hi,

 just realized the massive changes between 21 and 22. At least that is
answered :-) Question remains why no MC packets arrive in 2.4.22 and
later (checked with tcpdump). Is there anything that one has to enable
when running a newer kernel?

 One diffeernce is the output of "cat /proc/net/igmp". On my 2.4.20
kernel it looks like:

[qx29340@lpsdm16 ~]$ cat /proc/net/igmp
Idx     Device    : Count Querier       Group    Users Timer  Reporter
1       lo        :     0      V2
                                010000E0     1 0:F63C1223            0
2       eth0      :     1      V2
                                010000E0     1 0:F63C1225            0
3       eth1      :     2      V2
                                470B02EF     1 0:F63C2428            1
                                010000E0     1 0:F63C1225            0

 While on 2.4.22/23 it looks like:

qx29340@lpsdm20 linux-2.4.23-1-msc]$ cat /proc/net/igmp
Idx     Device    : Count Querier       Group    Users Timer Reporter
1       lo        :     0      V2
                                010000E0     1 0:FFFE5D5D           0
2       eth0      :     1      V2
                                010000E0     1 0:FFFE5D5D           0
3       eth1      :     2      V2
                                470B02EF     1 0:FFFF8D5D           0
                                010000E0     1 0:FFFE5D5D           0


 The difference seems to be the "reporter" flag for the 470B02EF
multicast group, which is exactely the adrress Ganglia uses.

Any ideas
Cheers
Martin
PS: Moved to linux-net

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

             reply	other threads:[~2004-01-05 15:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-05 15:02 Martin Knoblauch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-06 13:17 Any changes in Multicast code between 2.4.20 and 2.4.22/23 ? Martin Knoblauch
2004-01-06 11:11 Martin Knoblauch
     [not found] <OF82F2C5E5.10FE707F-ON88256E12.00701FFA@us.ibm.com>
2004-01-06  2:21 ` Martin Knoblauch
2004-01-06 12:59   ` Lawrence MacIntyre
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=20040105150252.13443.qmail@web13904.mail.yahoo.com \
    --to=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