Hi Ross,
Googeling I found https://bugzilla.redhat.com/show_bug.cgi?id=231899 that is
closed considering that it is not a bug.
Is it what you have in mind "Unfortunately at least some Linux kernel fanatics
don't think it's a bug" ?
In fact I used since many years the workaround of bind the socket to the
multicast group.
I tried on different kernel and used, something like a 3.4.x, the behaviour is
the same.
Regards,
Michel.
[@@THALES GROUP RESTRICTED@@]
De : live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] De la part de Ross Finlayson
Envoyé : mercredi 27 juin 2012 09:44
À : LIVE555 Streaming Media - development & use
Objet : Re: [Live-devel] multicast streams using same port
Yes, I read all that, and the sense I got from it is, Linux works one way,
everything else works another way. Thus my suggestion for a Linux-specific
ifdef wrapping the bind() call.
Yes, but I also recall someone reporting that they tried this, but it didn't
work for them (on Linux); apparently when they did this, they stopped receiving
packets at all.
But if people want to try this themselves, then they're welcome to. They
probably don't even need to modify the "groupsock" code; instead, they could
call "bind()" on the multicast address in their application code, immediately
after they've created a "Groupsock" object.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
