From: "Charles R. Anderson" <cra@WPI.EDU>
To: linux-kernel@vger.kernel.org
Subject: Re: v2.6 IGMPv3 implementation
Date: Mon, 12 Jul 2004 18:27:13 -0400 [thread overview]
Message-ID: <20040712222713.GK7822@angus.ind.WPI.EDU> (raw)
In-Reply-To: <20040712140409.3575b900.davem@redhat.com>
On Mon, Jul 12, 2004 at 02:04:09PM -0700, David S. Miller wrote:
> include/linux/in.h
> Specifically IP_MSFILTER and friends.
I noticed these. Do you have a pointer to documentation on this API?
Another thing I noticed. Which is better, __u32 or struct in_addr and
int? Both are used in include/linux/in.h for what appear to be the
same objects:
struct ip_mreq
{
struct in_addr imr_multiaddr; /* IP multicast address of group */
struct in_addr imr_interface; /* local IP address of interface */
};
struct ip_mreqn
{
struct in_addr imr_multiaddr; /* IP multicast address of group */
struct in_addr imr_address; /* local IP address of interface */
int imr_ifindex; /* Interface index */
};
struct ip_mreq_source {
__u32 imr_multiaddr;
__u32 imr_interface;
__u32 imr_sourceaddr;
};
struct ip_msfilter {
__u32 imsf_multiaddr;
__u32 imsf_interface;
__u32 imsf_fmode;
__u32 imsf_numsrc;
__u32 imsf_slist[1];
};
> BTW, unlike you claim, the IGMPv3 stack implementation has been in the
> kernel for a long time, much before 2.6.7 It is even in the current
> 2.4.x sources as well.
Thank you for clarifying. I only wish the userspace was caught up.
next prev parent reply other threads:[~2004-07-12 22:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 20:30 v2.6 IGMPv3 implementation Charles R. Anderson
2004-07-12 21:04 ` David S. Miller
2004-07-12 22:27 ` Charles R. Anderson [this message]
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=20040712222713.GK7822@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