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