From owner-freebsd-bugs@freebsd.org  Fri Dec 11 06:17:40 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1ABDC9D61AE
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Fri, 11 Dec 2015 06:17:40 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 0C6031EAC
 for <freebsd-bugs@FreeBSD.org>; Fri, 11 Dec 2015 06:17:40 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tBB6HduG097302
 for <freebsd-bugs@FreeBSD.org>; Fri, 11 Dec 2015 06:17:39 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 192014] getaddrinfo(3) broken in jail on loopback
Date: Fri, 11 Dec 2015 06:17:40 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 9.3-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: ume@FreeBSD.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: ume@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-192014-8-wqNy1YEf3m@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-192014-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-192014-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Dec 2015 06:17:40 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192014

Hajimu UMEMOTO <ume@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |In Progress
           Assignee|freebsd-bugs@FreeBSD.org    |ume@FreeBSD.org

--- Comment #10 from Hajimu UMEMOTO <ume@FreeBSD.org> ---
Created attachment 164104
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=164104&action=edit
Ignore just 127.0.0.1 instead of the whole loopback address range.

Yes, it is expected behavior from the spec of AI_ADDRCONFIG.  Since it was not
implemented correctly, your setup used to be working by chance.
Ignoring the loopback address is necessary to make AI_ADDRCONFIG usable. 
However, the loopback address except for 127.0.0.1 isn't used in a usual setup.
 Though it breaks a spec to be exact, there may be room for modifying
getaddrinfo(3) to ignore just 127.0.0.1 instead of the whole loopback address
range.
Does the attached patch work for you?

-- 
You are receiving this mail because:
You are the assignee for the bug.