JDK-6250763 : setTimeToLive function only effects IPv6 but it should be for both IPv4 and IPv6
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux_redhat_8.0
  • CPU: x86
  • Submitted: 2005-04-05
  • Updated: 2010-04-26
  • Resolved: 2007-06-28
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7
7Resolved
Related Reports
Duplicate :  
JDK-4742177 - Re-test IPv6 (and specifically MulticastSocket) with latest Linux & USAGI code
Description
J2SE Version (please include all output from java -version flag):
  java version "1.6.0-ea"
  Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-ea-b29)
  Java HotSpot(TM) Client VM (build 1.6.0-ea-b29, mixed mode, sharing)

Does this problem occur on J2SE 1.4.x or 5.0.x ?  
  Yes 

Operating System Configuration Information (be specific):
  Linux (Redhat 8 with the updated kernal 2.4.26) with 
  IPv6 module loaded

Bug Description:

When the IPv6 module loaded, MulticastSocket.setTimeToLive only effects
IPv6 defaultly. If sending packages to any IPv4 mulicast address, the
ttl og these packages are always 1, even MulticastSocket.getTimeToLive()
shows the socket has TTL set up to any number. It only works for IPv4,
only when disable IPv6 functions either by deleting all IPv6 address
or using java.net.preferIPv4Stack=true in the command line.

The right way is: the multicastSocket could send out both IPv4 and IPv6
packages. Therefore setTimeToLive function should effect both IPv4 and
IPv6. When sending out IPv6 packages, it effects hop limit; when sending
out IPv4 packages, it effects ttl.


###@###.### 2005-04-05 16:06:02 GMT
Comments
EVALUATION Unlike Solaris, configuring IPv6 socket options on IPv6 socket in Linux do not configure equivalent IPv4 options. We need to set both IPv4 and IPv6 (if IPv6 is available) options in Linux.
21-05-2007
EVALUATION Revisit this when Dolphin. ###@###.### 2005-07-18 02:05:17 GMT
18-07-2005