Hello I used to work under *BSD with Kame's kernel patch (inspired by Hitoshi Asaeda's patches) for IGMPv3 and MLDv2 host implementations, and t worked (not perfect but sufficient). As these protocols are now supported in the Linux Kernel, i'm trying to make my programs working with the SSM network service, but i have several problems (all is ok with MLDv1 and IGMPv2 operation). I'm running a 2.6.0-test1 kernel under a i686 environment, compiled with the IP multicasting option. When i take a look at the kernel sources, i can find the structures im supposed to use, which are both the IP independent ones, such as struct group_req or struct group_source_req or the operation codes such as MCAST_JOIN_GROUP, MCAST_JOIN_SOURCE_GROUP....., and the protocol specific ones, such as struct ipv6_mreq or struct ip_mreq_source, but i only find the protocol specific ones in /usr/include once the kernel is installed. I tride to define the protocol independent ones manually, it builds, but when running i have the following error when trying to join a channel : join_leave_ssm setsockopt : No such file or directory I knew i would have an error, but i don't understand much.... When using the protocol specific ones, it get a problem with the interface : if i give the correct interface address or the generic INADDR_ANY or in6addr_any i get the same error : join_leave_ssm setsockopt : No such device In fact, when i join the first channel in IPv4, everything is ok, and i receive the data, but when i try to join the followings ones, i get this error. For IPv6, i couldn't find the IPV6_ADD_SOURCE_MEMBERSHIP operation code or ipv6_mreq_source structure.... I wanted to know if someone has tride this and solved the problems i encountered. TIA Regards Fred _____________________________________________________________________ Envie de discuter en "live" avec vos amis ? Télécharger MSN Messenger http://www.ifrance.com/_reloc/m la 1ère messagerie instantanée de France - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
