Messages in this thread |  | | | Date | Mon, 12 Jul 2004 18:27:13 -0400 | | From | "Charles R. Anderson" <> | | Subject | Re: v2.6 IGMPv3 implementation |
| |
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.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |