JDK-8236184 : (dc) IP_MULTICAST_* and IP_TOS socket options not effective
- Type: Enhancement
- Component: core-libs
- Sub-Component: java.nio
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2019-12-18
- Updated: 2021-08-15
- Resolved: 2019-12-19
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.
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 15 |
|---|
15 b03Fixed  |
Related Reports
|
Blocks :
|
|
|
Relates :
|
|
|
Relates :
|
Description
Assuming IPv6 is enabled: If a DatagramChannel created with the no-arg open method is used to send IPv4 multicast datagrams then it is platform specific as to whether the IP_MULTICAST_XXX socket options are effective or not. The same thing arises with the IP_TOS socket option when sending IPv4 unicast or multicast datagrams. On Linux and Windows it is possible to set IP_MULTICAST_XXX and IP_TOS socket options on IPv6 sockets so that they are effective for IPv4 addresses. DatagramChannel should be updated to try to set the IPv4 socket options, this will be important for a future MulticastSocket implementation that uses a DatagramChannel under the covers.
Comments
|