[Live-devel] Concerning multicast TTL of zero

Martínez Contador, Daniel [ELIMCO] (CA) ELIMCO.dmartinez at navantia.es
Thu Feb 13 00:19:23 PST 2014


Hello.
For my application I need to send differently scoped multicast RTP.
I have found that I use both the multicast address and the TTL to try different configurations.
However, I cannot send multicast packets with a TTL of zero (meaning traffic restricted to the same host). They get sent but with a TTL of 1 (meaning traffic restricted to the same subnet, not what I want).
I have seen the problem lies in writeSocket in GroupsockHelper: it skips the setsockopt to set the TTL if it is 0.
Removing the condition seems to work (meaning such packets reach receivers in the same host but are not seen by other hosts in the subnet or traffic analysers), but I wonder if not setting TTL 0 is intentional and by enabling it I will be having "collaterals".
So, should everything work as expected when enabling TTL 0?
Would this be filed as a "bug" and be corrected in the next version?
I could send a patch, but that would make me a "contributor" and for just removing two obvious lines seems to much of a mention.

Best Regards.

Daniel Martínez Contador
Navantia - Sistemas de Control
Ctra. Algameca, s/n
30205 Cartagena (Murcia)
Tlfo: 968 323 387
Email: elimco.dmartinez at navantia.es


NAVANTIA
______________________________
Este mensaje, y cualquier fichero anexo al mismo, contiene informacion de caracter confidencial dirigida exclusivamente a su(s) destinatario(s) y, en su caso, sometida a secreto profesional. Queda prohibida su difusion, copia o distribucion a terceros sin la previa autorizacion escrita. Si Vd. ha recibido este mensaje por error, se ruega lo comunique inmediatamente por esta misma via y proceda a su completa eliminacion.
The information in this e-mail, and in any attachments, is confidential and, if any, protected by a professional privilege, and intended solely for the attention and use of the named addressee(s). You are hereby notified that any dissemination, copy or distribution of this information is prohibited without the prior written consent. If you have received this communication in error, please notify the sender by reply e-mail and delete it.
______________________________



More information about the live-devel mailing list