summaryrefslogtreecommitdiffstats
path: root/net/sunrpc/rpcb_clnt.c
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2008-08-18 19:33:44 -0400
committerJ. Bruce Fields <bfields@citi.umich.edu>2008-09-29 18:13:37 -0400
commitb6632339e3afbcbb438a3c8935190ea22464fc99 (patch)
tree13fb088ceb8b18563c2eae311b0007783a612948 /net/sunrpc/rpcb_clnt.c
parentc8ab5f2a13fb41a878863c61a1e27d78f1844b5e (diff)
downloadop-kernel-dev-b6632339e3afbcbb438a3c8935190ea22464fc99.zip
op-kernel-dev-b6632339e3afbcbb438a3c8935190ea22464fc99.tar.gz
SUNRPC: Set V6ONLY socket option for RPC listener sockets
My plan is to use an AF_INET listener on systems that support only IPv4, and an AF_INET6 listener on systems that can support IPv6. Incoming IPv4 packets will be posted to an AF_INET6 listener with a mapped IPv4 address. Max Matveev <makc@sgi.com> says: Creating a single listener can be dangerous - if net.ipv6.bindv6only is enabled then it's possible to create another listener in v4 namespace on the same port and steal the traffic from the "unifed" listener. You need to disable V6ONLY explicitly via a sockopt to stop that. Set appropriate socket option on RPC server listener sockets to prevent this. Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Diffstat (limited to 'net/sunrpc/rpcb_clnt.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud