Re: Windows 2000 problems
SSM is fundamentally different than AS Multicast in that you need to
specify a source ip address.
So instead of setsockopt(...IP_ADD_MEMBERSHIP...) you
setsockopt(..., IP_ADD_SOURCE_MEMBERSHIP, source_address, ...). To do this,
you really want IP_ADD_SOURCE_MEMERSHIP in the include files (or it won't
compile).
Any info on other semantics that Microsoft uses for SSM?
Quoting Kevin Gibbs <kgibbs --at-- ncsa.uiuc.edu>:
> Why do you think that you need special libraries or include files? The
> choice of IGMP versions would be made in the Window Sockets space. If you
> are trying to use Berkley socket symantics then you will be sadly
> disappointed. The Multicast symantics of Windows is very different. Check
> out the Platform SDK under Windows Socket Version 2 API it will lay out
> the semantics. If Microsoft follows its usual semantics it will allow an
> identical program to run IGMPv2 on a NT 3.51 - Win2k machine and if you
> run it on XP then boom you get IGMPv3. I have not seen any Berkley socket
> commands for the IGMPv3 host implementations (looked at the BSD and Linux
> ones) that can not be mimiced in some way with the Windows Socket
> interface. There is a few books on the subject specifically for Windows
> they may be worth looking into.
>
> Kevin
>
> On Fri, 21 Feb 2003 jzeeff --at-- internet2.edu wrote:
>
> >
> > Has anyone seen IGMPv3/SSM support in any of the Windows C development
> > tools? XP supports it, but without the library/include file support, not
> > much one can do.
> >
> >
> > > I have no experience with the cygwin environment so I can not help you
> > > out. I use Visual Studio .Net to compile win32 versions and the next
> > > release will include a .vcproj that can be used with VS .NET.
> > >
> >
>
>