Why is rpcbind using port 906?

Garrett Cooper youshi10 at u.washington.edu
Tue Jan 9 10:54:39 PST 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The last time I checked rpcbind was supposed to run on port 111

[root at hoover /home/gcooper]# uname -a
FreeBSD hoover.localdomain 6.1-RELEASE-p11 FreeBSD 6.1-RELEASE-p11 #18:
Thu Dec 21 09:00:56 PST 2006
gcooper at hoover.localdomain:/usr/obj/usr/src/sys/HOOVER  i386
[root at hoover /home/gcooper]# lsof | grep rpcbind | grep IPv
lsof: WARNING: compiled for FreeBSD release 6.1-RELEASE-p10; this is
6.1-RELEASE-p11.
rpcbind     375    root    4u  IPv6 0xc67515a0        0t0     UDP *:*
rpcbind     375    root    6u  IPv6 0xc6751438        0t0     UDP *:sunrpc
rpcbind     375    root    7u  IPv6 0xc67512d0        0t0     UDP *:1023
rpcbind     375    root    8u  IPv6 0xc67bb000        0t0     TCP
*:sunrpc (LISTEN)
rpcbind     375    root    9u  IPv4 0xc6751168        0t0     UDP *:sunrpc
rpcbind     375    root   10u  IPv4 0xc6751000        0t0     UDP *:906
rpcbind     375    root   11u  IPv4 0xc67bacb0        0t0     TCP
*:sunrpc (LISTEN)

Is there some way to change the default port to something static?
manpage doesn't say so, but there may be an option.

Annoying, but it appears that some smbclients _need_ to have rpcbind's
port unblocked by a firewall; blocking it broke some functionality with
mounting SMB shares on non-Windows clients.

TIA,
- -Garrett
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.1 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFo+TrEnKyINQw/HARArH0AKCm07971prNO+/MYXIEuISO+bRTowCgp8qL
Qs1VFiQ61nuAu6Cx8l8f3FE=
=RhKO
-----END PGP SIGNATURE-----


More information about the freebsd-net mailing list