The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Martin Knoblauch <knobi@knobisoft.de>
To: David Stevens <dlstevens@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: Any changes in Multicast code between 2.4.20 and 2.4.22/23 ?
Date: Tue, 6 Jan 2004 03:11:06 -0800 (PST)	[thread overview]
Message-ID: <20040106111106.55456.qmail@web13902.mail.yahoo.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 893 bytes --]

>> 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 :-)?

 so, I append two traces from "tcpdump -i eth1 multicast". "good" is
from the 2.4.20.-18.7smp kernel, "bad" is from 2.4.22.

 What is interesting from a first look is the fact that the 2.4.22
kernel seems to drop/miss packets from outside that go to a
nonpriviledged port on the multicast group. Ganglia uses port 8649. In
the "bad" case, packets for "239.2.11.71.8649" only come from the local
box. Does this ring any bells for "tg3" or the networking code?

Cheers
Martin

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

[-- Attachment #2: bad.tcpdump --]
[-- Type: application/octet-stream, Size: 9596 bytes --]

[-- Attachment #3: good.tcpdump --]
[-- Type: application/octet-stream, Size: 8612 bytes --]

             reply	other threads:[~2004-01-06 11:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-06 11:11 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
     [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 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=20040106111106.55456.qmail@web13902.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