netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Pietikainen <pp@ee.oulu.fi>
To: James Hubbard <jameshubbard@gmail.com>
Cc: netdev@oss.sgi.com
Subject: Re: Broadcom 4400 driver bm44
Date: Thu, 8 Jul 2004 16:38:53 +0300	[thread overview]
Message-ID: <20040708133853.GA20254@ee.oulu.fi> (raw)
In-Reply-To: <f3ddc6d3040707112141b20720@mail.gmail.com>

On Wed, Jul 07, 2004 at 02:21:49PM -0400, James Hubbard wrote:
> I have two apps (AppA and AppB) that communicate via multicast.   The
> initial discovery process allows the apps to find each other.  The
> apps send hearbeats periodically to advertise that they are on the
> network.  After a period of time,  AppB can't see AppA.   I would say
> that AppB stops seeing AppA after the initial discovery.  I say this
> If I use this command: 
> ifconfig eth0 allmulti
> AppB receives all of the multicast data and can receive data from
> AppA.  This in turn  causes a problem where standard communication via
> TCP does not function.  Pings, ssh, etc do not work. If I disable
> allmulti. All other communication works except for multicast.

Hiya

I'll try to reproduce the problem. It's entirely possible that there's 
something wrong in the multicast filter code. What would be helpful is
some sort of quick testcase that shows this problem. I tried
a minimal multicast test program (mcast.py from the python distribution)
and that worked ok. ifconfig eth1 allmulti did cause the connection
to my home box to hang, so that I can reproduce at least ;) ;) ;)

       reply	other threads:[~2004-07-08 13:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f3ddc6d3040707112141b20720@mail.gmail.com>
2004-07-08 13:38 ` Pekka Pietikainen [this message]
     [not found]   ` <f3ddc6d304070807002a19d340@mail.gmail.com>
2004-07-08 20:43     ` Broadcom 4400 driver bm44 Pekka Pietikainen
2004-07-26 13:49       ` James Hubbard

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=20040708133853.GA20254@ee.oulu.fi \
    --to=pp@ee.oulu.fi \
    --cc=jameshubbard@gmail.com \
    --cc=netdev@oss.sgi.com \
    /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).