Date: Fri, 6 Jan 2006 01:40:24 -0800 From: James Long <stable@museum.rain.com> To: freebsd-stable@freebsd.org Cc: Vivek Khera <vivek@khera.org> Subject: Re: rpcbind lingering on IP no longer specified on command line Message-ID: <20060106094024.GA43299@ns.museum.rain.com> In-Reply-To: <20060106040839.A38DE16A46C@hub.freebsd.org>
index | next in thread | previous in thread | raw e-mail
> Date: Thu, 5 Jan 2006 10:31:33 -0500 > From: Vivek Khera <vivek@khera.org> > Subject: Re: rpcbind lingering on IP no longer specified on command > line > To: stable@freebsd.org > Message-ID: <51DD97C7-4002-4459-A709-1B72DC1189A7@khera.org> > Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed > > > On Jan 5, 2006, at 6:06 AM, Gavin Atkinson wrote: > > >> Can anyone explain why rpcbind will still bind to all tcp interfaces? > > > > Although I believe this is a bug, it is actually working as > > documented: > > > > from rpcbind(8): > > -h bindip > > Specify specific IP addresses to bind to for UDP > > requests. > > Yeah, I noticed that little tiny "UDP requests" note in the -h docs > too. There's no reason to bind to all tcp addresses, and it is > causing me heartburn for getting the server certified... Good grief, why not just firewall off the undesired UDP ports and call it good?home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060106094024.GA43299>