From owner-freebsd-apache@FreeBSD.ORG Mon Mar 17 16:30:01 2014 Return-Path: Delivered-To: apache@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9CCEDD38 for ; Mon, 17 Mar 2014 16:30:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2FD2B9C3 for ; Mon, 17 Mar 2014 16:30:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s2HGU1NP014153 for ; Mon, 17 Mar 2014 16:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s2HGU1fP014152; Mon, 17 Mar 2014 16:30:01 GMT (envelope-from gnats) Date: Mon, 17 Mar 2014 16:30:01 GMT Message-Id: <201403171630.s2HGU1fP014152@freefall.freebsd.org> To: apache@FreeBSD.org From: The BSD Dreamer Subject: Re: ports/187561: devel/subversion: bogus "No route to host" caused by www/serf X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: The BSD Dreamer List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Mar 2014 16:30:01 -0000 The following reply was made to PR ports/187561; it has been noted by GNATS. From: The BSD Dreamer To: olli hauer Cc: bug-followup@freebsd.org Subject: Re: ports/187561: devel/subversion: bogus "No route to host" caused by www/serf Date: Mon, 17 Mar 2014 11:24:43 -0500 Looks like the patch is try all the addresses returned for a host. Instead of giving up on the first one because APR prefers ipv6 over ipv4. I suppose I could rebuild the APR dependency without the IPV6 default option as another fix. My guess is that there's something else that makes it skip trying IPv6 if there are no interfaces with IPv6, but the logic doesn't know to ignore lo0 when looking to see if there are any? Digging a bit....there's a comment (apr1 source: network_io/unix/sockaddr.c) that per RFC "...does not consider loopback addresses when trying to determine if IPv4 or IPv6 is configured on a system", so that matches allowing IPv6 to remain enabled on loopback. But, it goes on saying "This is a problem if one actually wants to listen on or connect to loopback address of a protocol that is not otherwise configured on the system"...so it works around that. With a note that the routine should accept a flag to determine if the work around is wanted. So sounds like APR forces loopback in for determining if IPv6 is enabled or not. Which would explains why my disabling IPv6 on loopback worked. On 2014-03-16 06:40, olli hauer wrote: > Hi Lawrence, > > there was a PR about an IPv6 issue on upstream and a fix is included since > serf-1.3.3. > http://code.google.com/p/serf/issues/detail?id=129 > > That's the changed part in serf/outgoing.c > http://code.google.com/p/serf/source/diff?spec=svn2187&r=2187&format=side&path=/trunk/outgoing.c > > I haven't seen and cannot confirm the issue here, even with an IPv6 address > on any of the interfaces on my test system. > At the moment I have no idea why this happened on your system. -- Name: Lawrence "The Dreamer" Chen Call: W0LKC Snail: 1530 College Ave, A5 Email: beastie@tardisi.com Manhattan, KS 66502-2768 Blog: http://lawrencechen.net