On Fri, 2017-02-24 at 11:02 +0000, Stuart Henderson wrote: > On 2017/02/23 13:43, Kurt Miller wrote: > > > > This eliminates the with_ipv6 FLAVOR in favor of a different > > approach. > > ipv6 support will be compiled into the default packages, however I > > have > > set preferIPv4Stack to default to true. The result should be no > > change > > for ipv4 users but would allow the use of ipv6 by setting some > > properties. Here's what I put in the DESCR: > > > > NOTE: > > ipv4 to ipv6 address mapping is disabled on OpenBSD. This means the > > jdk can only use ipv4 addresses or ipv6 addresses but not both at > > the same time. By default ipv4 addresses are enabled. To use ipv6 > > addresses set the following properties when you start java: > > > > -Djava.net.preferIPv4Stack=false > > -Djava.net.preferIPv6Stack=true > > -Djava.net.preferIPv6Addresses=true > > > > Testing that I have not broken ipv4 use cases would be greatly > > appreciated. Testing ipv6 works with the three properties would get > > bonus points. > I had to hand-apply the patch due to UTF-8 non-breaking spaces in the > email, IPv4 works, IPv6 works with the flags. This is much better > than > the separate flavour, so OK with me. > > As expected, it's not possible to connect to a v4 address if the v6 > flags are in use, so the only practical way I see to be able to use > both > protocols from the same process is by using the v6 flags and running > NAT64 + DNS64 and connecting by DNS name rather than raw IP. Software > like UniFi which wants to connect explicitly to 127.0.0.1 won't work > this way. >
Thanks for testing it. Should we add any of this text to DESC? I put the PLIST changes in from your other email. Thanks for catching that. I'll wait a few days to see if there is any more feedback before committing. -Kurt
