i386/88320: ypxfr talks IPv6 to IPv4-only portmap -> ypinit fails

Martin nobody at junk.com
Tue Nov 1 03:40:18 PST 2005

>Number:         88320
>Category:       i386
>Synopsis:       ypxfr talks IPv6 to IPv4-only portmap -> ypinit fails
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-i386
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Nov 01 11:40:16 GMT 2005
>Originator:     Martin
>Release:        RELENG_6_0 as of 2005-10-30 + RELENG_4_11_0_RELEASE
FreeBSD marvin.xyzzy 6.0-RC1 FreeBSD 6.0-RC1 #0: Mon Oct 31 09:12:20 CET 2005     root at marvin.xyzzy:/usr/VOL/OBJ/FreeBSD/RELENG_6_0/src/sys/MARVIN  i386

I have a dual IPv4/IPv6 setup and am trying to ypinit a slave machine
running RELENG_6 from a master server running RELENG_4_11_0_RELEASE.

The symptom is that ypinit simply hangs and does nothing.

The reason is that ypxfr tries to contact portmap on the 4.11 machine via
IPv6, but on 4.11 portmap only listens on IPv4.

A workaround is to delete all AAAA entries from /etc/hosts and stop the
name server, such that the rpc call uses only an IPv4 address.
run ypinit -s ... on a FreeBSD6 machine against a FreeBSD4 yp server.
rpc should cycle through all available host addresses if it cannot reach a host via a specific address (similar to what telnet does).

More information about the freebsd-i386 mailing list