rpcbind lingering on IP no longer specified on command line
James Long
stable at museum.rain.com
Fri Jan 6 01:40:31 PST 2006
> Date: Thu, 5 Jan 2006 10:31:33 -0500
> From: Vivek Khera <vivek at khera.org>
> Subject: Re: rpcbind lingering on IP no longer specified on command
> line
> To: stable at freebsd.org
> Message-ID: <51DD97C7-4002-4459-A709-1B72DC1189A7 at 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?
More information about the freebsd-stable
mailing list