On 29/11/2018 20:29, Michael McMahon wrote:
:
I've updated the webrev after the last comments:
http://cr.openjdk.java.net/~michaelm/8211842/webrev.2/
It's really just refactoring. So, unless anyone has a comment I will push
the fix shortly.
Thanks for the update, this version looks good to me
Yes, as Alan said the way IPv6 is set up in the JDK means that either
you have:
AF_INET sockets (which are IPv4 only) or
AF_INET6 sockets (which can be IPv4 or IPv6)
It's not possible to mix the two types. If inetd passes an AF_INET
socket on startup then the VM is stuck in IPv4 mode.
I've upd
On 29/11/2018 18:04, Bernd Eckenfels wrote:
Hello,
I wonder if that conclusion „stdin = tcp4 -> disable tcp6“ is correct
at all. The started program might serve a v4 connection but it still
could want to do ipv6 client connections.
If somebody wants to disable v4 they can do it regularly wi
ttp://bernd.eckenfels.net
Von: Michael McMahon
Gesendet: Mittwoch, 28. November 2018 17:22
An: OpenJDK Network Dev list
Betreff: RFR: 8211842 IPv6_supported wrongly returns false when unix
domainsocket is bound to fd 0
Could I get the following fix reviewed please?
The fix is pretty simple, but
