public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Charles R. Anderson" <cra@WPI.EDU>
To: linux-kernel@vger.kernel.org
Subject: v2.6 IGMPv3 implementation
Date: Mon, 12 Jul 2004 16:30:56 -0400	[thread overview]
Message-ID: <20040712203056.GI7822@angus.ind.WPI.EDU> (raw)

Please Cc any replies directly to my address, since I am not
subscribed.  Thanks.

I'm taking a look at the IGMPv3 implementation that was integrated
into the 2.6 kernel (2.6.7 specifically).  In the past there have been
patches floating around that implemented the IGMPv3 stack, and these
provided some new IOCTLs:

/* Multicast source filter calls */
#define SIOCSIPMSFILTER        0x89a0          /* set mcast src filter (ipv4) */
#define SIOCGIPMSFILTER 0x89a1         /* get mcast src filter (ipv4) */
#define SIOCSMSFILTER  0x89a2          /* set mcast src filter (proto indep) */
#define SIOCGMSFILTER  0x89a3          /* get mcast src filter (proto indep) */

These do not appear in the Linus kernel, though.  Does anyone know the
status of these ioctls and the IGMPv3 implementation in general?  I'm
trying to get the proper bits stuffed into glibc to make IGMPv3/SSM
usable, and I'm not sure what to do about these ioctls.  Should 4 new
ioctl numbers be reserved for these in case an implementation is
integrated, or should I just leave them out of glibc headers entirely?

Thanks.


             reply	other threads:[~2004-07-12 20:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-12 20:30 Charles R. Anderson [this message]
2004-07-12 21:04 ` v2.6 IGMPv3 implementation David S. Miller
2004-07-12 22:27   ` Charles R. Anderson
2004-07-12 22:48     ` YOSHIFUJI Hideaki / 吉藤英明
2004-07-12 21:22 ` YOSHIFUJI Hideaki / 吉藤英明
2004-07-13  1:21   ` Charles R. Anderson
2004-07-13  1:51     ` YOSHIFUJI Hideaki / 吉藤英明

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=20040712203056.GI7822@angus.ind.WPI.EDU \
    --to=cra@wpi.edu \
    --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