This is the mail archive of the
mailing list for the Cygwin project.
Re: Portmap RPC registration fails
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 9 May 2012 20:20:02 +0200
- Subject: Re: Portmap RPC registration fails
- References: <email@example.com>
- Reply-to: cygwin at cygwin dot com
On May 8 22:41, Ken wrote:
> Further to this post... With a struggle I built libtirpc.a and traced
> execution. Ultimately this is failing in clnt_vc.c. The following call in
> connect(fd, (struct sockaddr *)raddr->buf, raddr->len)
> supplies an IPV6 address with hex values:
> 006F 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001 0000 0000 3300
> The codes's own diagnostics report:
> Got ua [::1.0.111]
> netbuf len = 28, maxlen = 28
> Address is 126.96.36.199.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.0.0.0.
> rpcbind clnt interface: RPC: Remote system error - Connection refused
> The above doesn't look like a plausible IPV6 address. I have IPV6 enabled on
> my network adapter. Is it possible that portmap isn't compatible with IPV6?
> That would explain why older code (such as CygWin NFS Server - IPV4) is able
> to register with portmap.
portmap and the entire sunrpc package is pretty old stuff. They are not
used anymore on Linux and BSD afaik, but there's replacement code in a
not so easy portable way.
Portmap and the rest of the sunrpc code is not overly complicated, though.
With a bit of effort it should be possible to make it IPv6-aware. However,
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple