[jboss-jira] [JBoss JIRA] (JGRP-1880) UDP.ip_ttl is ignored and is always 1
Bela Ban (JIRA)
issues at jboss.org
Thu Sep 4 04:03:59 EDT 2014
[ https://issues.jboss.org/browse/JGRP-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998698#comment-12998698 ]
Bela Ban commented on JGRP-1880:
--------------------------------
Class {{DatagramChannel}} has the ability to set {{IP_MULICAST_TTL}} as an option. Investigate whether we can use a {{DatagramChannel}} instead of a {{DatagramSocket}}. Perhaps we can create a {{DatagramChannel}}, but then call {{DatagramChannel.socket()}} to simply use the underlying {{DatagramSocket}} instead.
> 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
> Security Level: Public(Everyone can see)
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 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.1#6329)
More information about the jboss-jira
mailing list