[jboss-jira] [JBoss JIRA] (JGRP-1880) UDP.ip_ttl is ignored and is always 1

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023069#comment-13023069 ] 

Bela Ban edited comment on JGRP-1880 at 11/26/14 6:18 AM:
----------------------------------------------------------

There's a problem on Windows where setting the TTL throws a 'not implemented' exception. This is caused by not using the right stack, forcing IPv4 with {{-Djava.net.preferIPv4Stack=true}} fixes this. Details at https://github.com/belaban/JGroups/wiki/FAQ


was (Author: belaban):
There's a problem on Windows where setting the TTL throws a 'not implemented' exception. This is caused by not using the right stack, forcing IPv4 with {{-Djava.net.preferIPv4Stack=true}} fixes this.

> UDP.ip_ttl is ignored and is always 1
> -------------------------------------
>
>                 Key: JGRP-1880
>                 URL: https://issues.jboss.org/browse/JGRP-1880
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 3.5.1, 3.6
>
>
> Since we switched from using a {{MulticastSocket}} for sending of multicast packets to a {{DatagramSocket}}, the time-to-live (TTL) of a packet is always {{1}}. The reason is that method {{setTimeToLive()}} only exists in {{MulticastSocket}}, but not in {{DatagramSocket}}.
> We cannot revert the code and use a {{MulticastSocket}} to send multicasts, as this won't reveal the real IP address of the sender, but only the multicast address, and the real address is needed to drop packets at the _transport level_.
> Investigate whether we could use reflection to get the {{DatagramSocketImpl}} and call {{setTimeToLive()}}.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)