[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: IPv6 support for yp/NIS
On Wed, Dec 10, 2008 at 07:43:57PM +0000, Christos Zoulas wrote:
> In article <20081210190548.GA8288%NetBSD.org@localhost>,
> Brian Ginsbach <ginsbach%NetBSD.org@localhost> wrote:
> >On Wed, Dec 10, 2008 at 06:28:31PM +0000, Christos Zoulas wrote:
> >> In article <20081209045753.GC16469%mewburn.net@localhost>,
> >> Luke Mewburn <lukem%NetBSD.org@localhost> wrote:
> >> >-=-=-=-=-=-
> >> >
> >> >On Fri, Oct 03, 2008 at 05:36:04PM -0400, Glen R. J. Neff wrote:
> >> > | I find myself in one hell of a conundrum. I need an NIS server that
> >> > | supports IPv6.
> >> > |
> >> > | I initially tried with FreeBSD but found that every piece of the yp
> >> > | suite supported IPv6 except ypserv.
> >> > |
> >> > | Then someone told me that NetBSD's ypserv supported it, so I gave it a
> >> > | try, and they're right, it does! But you know what, in the case of
> >> > | NetBSD, every piece of the yp suite supports IPv6 except ypbind.
> >> >
> >> >Have you submitted a PR about the lack of IPv6 in ypbind?
> >> >Less likely for the problem to be forgotten about that way.
> >> Isn't the problem that RPC does not really support anything but IPv4?
> >If that is really the case then there are a bunch of NetBSD RPC
> >programs needlessly opening IPv6 ports.
> How does one deal with things that use struct sockaddr_in *
> svc_getcaller(SVCXPRT *xprt), like ypbind does?
Use svc_getrpccaller(SVCXPRT *xprt) which is the "transport neutral"
> >The problem is that ypbind version 2 only knows about IPv4. I'm
> >looking into adding support for version 3 ala Sun's later version
> >of ypbind.
> Isn't that for NIS+? (I am clueless)
Not that I'm aware. This is version 3 of the ypbind protocol. It
is to support, as far as I can tell, "transport neutral" binding.
I believe that NIS+ falls under a different RPC program (100300)
vs. NIS a.k.a YP (100004).
Main Index |
Thread Index |