From owner-freebsd-current@freebsd.org Tue Feb 12 18:41:20 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5B0114F09E9 for ; Tue, 12 Feb 2019 18:41:20 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4862174407; Tue, 12 Feb 2019 18:41:20 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:13b:39f::9f:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) (Authenticated sender: bz/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 0F20813C31; Tue, 12 Feb 2019 18:41:20 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 591EE8D4A175; Tue, 12 Feb 2019 18:41:17 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 4BF2BD23102; Tue, 12 Feb 2019 18:41:16 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id LawRHibFpxBO; Tue, 12 Feb 2019 18:41:14 +0000 (UTC) Received: from [192.168.2.110] (unknown [IPv6:fde9:577b:c1a9:31:2ef0:eeff:fe03:ee34]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id D2970D23103; Tue, 12 Feb 2019 18:41:14 +0000 (UTC) From: "Bjoern A. Zeeb" To: "Rick Macklem" Cc: freebsd-current@FreeBSD.org Subject: Re: what do jails map 127.0.0.1 to? Date: Tue, 12 Feb 2019 18:41:14 +0000 X-Mailer: MailMate (2.0BETAr6135) Message-ID: <2F884512-F6A4-4E37-8566-46985A9FC5E3@FreeBSD.org> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4862174407 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.97 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; NEURAL_HAM_SHORT(-0.98)[-0.977,0]; ASN(0.00)[asn:11403, ipnet:96.47.64.0/20, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2019 18:41:20 -0000 On 11 Feb 2019, at 0:50, Rick Macklem wrote: > I am finally back to looking at an old PR#205193. > > The problem is that the nfsuserd daemon expects upcalls from the > kernel > that are from localhost (127.0.0.1) and when jails are running on the > system, > 127.0.0.1 is mapped to some other IP#. (I think it might be the > address of the > first net interface on the machine, but I'm not sure?) And what does it do on system that have no 127.1 or no IPv4 at all anymore or don’t even support IPv4 anymore? > Is there a way that nfsuserd.c can find out what this IP# is? Yes, could do easily but wouldn’t work for my above case, would it? I can help you with the code for v4 and jails if you help me with the code for IPv6? > (I have a patch that converts nfsuserd.c to using an AF_LOCAL socket, > but that > breaks for some setups. I think it was when the directory the socket > was being > created in is NFSv4 mounted, but I can't remember exactly how it > fails.) > > Thanks for any help with this, rick > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org"