On Nov 7, 2011, at 11:23 AM, Steve Dickson wrote:
>
>
> On 11/06/2011 10:58 AM, Jim Rees wrote:
>> Is there some good reason why the rpcbind '-h' option (bind to given
>> address) applies only to the udp listening socket and not to the tcp socket?
> No... sounds like a bug to me...
Behavior is described right in the man page. So this seems to be on purpose.
-h Specify specific IP addresses to bind to for UDP requests. This option
may be specified multiple times and is typically necessary when running
on a multi-homed host. If no -h option is specified, rpcbind will bind
to INADDR_ANY, which could lead to problems on a multi-homed host due to
rpcbind returning a UDP packet from a different IP address than it was
sent to. Note that when specifying IP addresses with -h, rpcbind will
automatically add 127.0.0.1 and if IPv6 is enabled, ::1 to the list.
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
