Date: Fri, 6 Jan 2006 15:42:32 +0000 From: Ceri Davies <ceri@submonkey.net> To: Dmitry Morozovsky <marck@rinet.ru> Cc: Vivek Khera <vivek@khera.org>, stable@freebsd.org Subject: Re: rpcbind lingering on IP no longer specified on command line Message-ID: <20060106154232.GF86645@submonkey.net> In-Reply-To: <20060106173204.P87428@woozle.rinet.ru> References: <A97CE7DE-1841-41D0-B702-E82761FCDD3B@khera.org> <20060104222846.K98554@woozle.rinet.ru> <20060106103648.GJ31522@submonkey.net> <20060106173204.P87428@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--wjoFZxbW4tu+iR6v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 06, 2006 at 05:35:28PM +0300, Dmitry Morozovsky wrote: > On Fri, 6 Jan 2006, Ceri Davies wrote: >=20 > CD> > VK> I had rpcbind running with on two interfaces like this: > CD> > VK>=20 > CD> > VK> rpcbind -h 192.168.100.200 -h 10.0.0.9 > CD> > VK>=20 > CD> > VK> Now, I changed rpcbind_flags in /etc/rc.conf to just have the f= irst address, > CD> > VK> and I restarted rpcbind. the process list from ps shows it is = running like > CD> > VK> this: > CD> > VK>=20 > CD> > VK> rpcbind -h 192.168.100.200 > CD> > VK>=20 > CD> > VK> Yet nmap on the other address shows rpcbind is still listening = on udp there. > CD> > VK> How do I stop that? > CD> >=20 > CD> > As I sometimes looked into this, rpcbind (formely portmap) listens = on all=20 > CD> > described addresses via udp *and* an tcp:*.111 - I tried to dig why= is this but=20 > CD> > did not succeed much. > CD>=20 > CD> Please test this patch. It's probably a very naive fix, but seems to > CD> work OK. >=20 > Well, two objections: >=20 > - (obvious and dumb ;): three kinds of changes inside: behaviour, style a= nd=20 > typo ;-))) Well yeah, but I figured that didn't matter for now. I disagree that the RUN_AS stuff is style though; the previous hardcoded "daemon" completely takes away the point of the '#define RUN_AS "daemon"'. If you are referring to my indentation, again that's just a "keep the patch simple" thing. Anyway... > - serious: no way to run on NO_INET6 kernel: >=20 > root@mole:/usr/src/usr.sbin/rpcbind# pid rpc > 83231 ?? Ss 0:00.00 /usr/obj/ar/src.6/usr.sbin/rpcbind/rpcbind > root@mole:/usr/src/usr.sbin/rpcbind# killall rpcbind > root@mole:/usr/src/usr.sbin/rpcbind# pid rpc > root@mole:/usr/src/usr.sbin/rpcbind# rpcbind > root@mole:/usr/src/usr.sbin/rpcbind# rpcinfo -p > program vers proto port service > 100000 4 tcp 111 rpcbind > 100000 3 tcp 111 rpcbind > 100000 2 tcp 111 rpcbind > 100000 4 udp 111 rpcbind > 100000 3 udp 111 rpcbind > 100000 2 udp 111 rpcbind > 100000 4 local 111 rpcbind > 100000 3 local 111 rpcbind > 100000 2 local 111 rpcbind > root@mole:/usr/src/usr.sbin/rpcbind# killall rpcbind > root@mole:/usr/src/usr.sbin/rpcbind# /usr/obj/ar/src.6/usr.sbin/rpcbind/r= pcbind > root@mole:/usr/src/usr.sbin/rpcbind# rpcinfo -p > rpcinfo: can't contact portmapper: RPC: Port mapper failure - RPC: Success > root@mole:/usr/src/usr.sbin/rpcbind# sockstat -4 | grep rpc > root rpcbind 83332 7 udp4 *:111 *:* > root rpcbind 83332 8 udp4 *:608 *:* > root rpcbind 83332 9 tcp4 *:111 *:* That's more annoying. It's not INET6 though; it's because the local transport is also tpi_cots_ord, so /var/run/rpcbind.sock is not getting created. I'll take another go at this over the weekend. Ceri --=20 Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. -- Einstein (attrib.) --wjoFZxbW4tu+iR6v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDvo/oocfcwTS3JF8RAu81AJ4r/8hTqZB+RYHxq7GxfIXVD1XDcACgvU+t JbrajR1idB3Oe+1PQ63rXi8= =dppg -----END PGP SIGNATURE----- --wjoFZxbW4tu+iR6v--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060106154232.GF86645>