public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Wesley W. Terpstra" <terpstra@gkec.tu-darmstadt.de>
To: linux-kernel@vger.kernel.org
Subject: Broken? 2.6.6 + IP_ADD_SOURCE_MEMBERSHIP + SO_REUSEADDR
Date: Fri, 4 Jun 2004 17:54:23 +0200	[thread overview]
Message-ID: <20040604155423.GA5656@muffin> (raw)

Hi!

I am using the new IGMPv3 support in the 2.6.* series for Single Source
Multicast (SSM). However, the kernel appears to (incorrectly) drop packets
in some situations.

What I do is this: open a UDP port, set it SO_REUSEADDR, bind it to port
6767, and then use IP_ADD_SOURCE_MEMBERSHIP to listen to multicast group 
232.65.43.21 and with a command-line controlled sender.

If I launch the same program twice with different senders, the first program
ceases to receive multicast packets. (Neither from its own sender, nor the
second program's sender) The second program receives packets from its
designated sender only (as expected).

I know from tcpdump that the switch is delivering messages from the first
designated sender. The kernel is simply not giving them to the application.

Some more observations:

If both programs specify the same sender, then both programs receive the
message (as expected).

This is not an issue with subscribing to multiple senders in general. A
single program listening to two senders does receive messages from both.

This seems like a bug to me.

PS. I am not subscribed to this list, so please CC me.

-- 
Wesley W. Terpstra

             reply	other threads:[~2004-06-04 15:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04 15:54 Wesley W. Terpstra [this message]
2004-06-04 16:55 ` Broken? 2.6.6 + IP_ADD_SOURCE_MEMBERSHIP + SO_REUSEADDR YOSHIFUJI Hideaki / 吉藤英明
     [not found]   ` <20040604212916.GA6683@muffin>
2004-06-04 21:29     ` David S. Miller

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=20040604155423.GA5656@muffin \
    --to=terpstra@gkec.tu-darmstadt.de \
    --cc=linux-kernel@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