Date: Tue, 12 Feb 2019 18:41:14 +0000 From: "Bjoern A. Zeeb" <bz@FreeBSD.org> To: "Rick Macklem" <rmacklem@uoguelph.ca> Cc: freebsd-current@FreeBSD.org Subject: Re: what do jails map 127.0.0.1 to? Message-ID: <2F884512-F6A4-4E37-8566-46985A9FC5E3@FreeBSD.org> In-Reply-To: <QB1PR01MB3537028815A3502AA6BC4B9BDD640@QB1PR01MB3537.CANPRD01.PROD.OUTLOOK.COM> References: <QB1PR01MB3537028815A3502AA6BC4B9BDD640@QB1PR01MB3537.CANPRD01.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2F884512-F6A4-4E37-8566-46985A9FC5E3>