Date: Tue, 09 Jan 2007 10:54:36 -0800 From: Garrett Cooper <youshi10@u.washington.edu> To: freebsd-net@freebsd.org Subject: Why is rpcbind using port 906? Message-ID: <45A3E4EC.5030403@u.washington.edu>
next in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The last time I checked rpcbind was supposed to run on port 111 [root@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@hoover.localdomain:/usr/obj/usr/src/sys/HOOVER i386 [root@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-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45A3E4EC.5030403>