On Monday, January 26, 2015 21:40 CET, Stuart Henderson <st...@openbsd.org> wrote: > On 2015/01/26 13:52, trondd wrote: > > On 1/26/15, Sebastian Reitenbach <sebas...@l00-bugdead-prods.de> wrote: > > > > > > > > It seems, since it worked, java got updated, at least when it worked, I > > > had > > > the java version 7u65, now I have the 7u71. > > > But don't know if the Java update might have caused the trouble, or > > > something else in the IPv6 stack? > > > > > > I'm going to try build and installing the 7u65, in order to see if that > > > helps. > > > > > > Does anyone else has luck with a current snapshot, java 7u71 and IPv6? > > > > > > Sebastian > > > > A quick look at the JDK ports Makefile shows a separate "with_ipv6" > > flavor. Doesn't look like that flavor is built and published to > > mirrors, though. It might be broken or just not in high demand. Not > > sure. > > > > If you are building from ports, make sure you build the right flavor. > > > > Tim. > > > > Note the warnings in DESCR: Java doesn't have great multi-AF support, > it relies on OS mapping that OpenBSD intentionally doesn't allow. > I already recognized that one earlier. However, I usually only installed the default jdk package, and that was able to do IPv6 or IPv4, but I did not got it to do both at the same time. Maybe the older versions didn't really catched the DONT_ENABLE_IPV6="YES"? At least that's what I figured worked so far with puppetdb. Java 7u65 default flavor is still building, I'll see if this allows IPv6 on the current snapshot.
Anyways, with IPv6 disabled by default, does this with_ipv6 java flavor make sense at all? With no IPv6, shouldn't it just fall back and operate on IPv4? Or you use the parameters -Djava.net.preferIPv6Addresses=true or -Djava.net.preferIPv4Addresses=true. Still have to test, whenever its finished building. Sebastian
