Description of problem: Case1:- ------ when nfs.rpc-auth-allow is set to an ip_address, it should allow nfs mount request only from the ip_address specified as value to nfs.rpc-auth-allow. Case2:- ----- when nfs.rpc-auth-reject is set to an ip_address, any nfs mount requests from the ip_address should be rejected. Version-Release number of selected component (if applicable): mainline How reproducible: often Steps to Reproduce Case1: ------------------------- 1.gluster volume set <vol_name> nfs.rpc-auth-allow <client1> 2.mount -t nfs -o vers=3 <volume> <mount_point> from client1 Actual results: [2012-03-02 18:42:16.653885] T [mount3.c:767:mnt3_check_client_net] 0-nfs-mount: Peer not allowed [2012-03-02 18:42:16.653917] D [mount3.c:913:mnt3svc_mnt] 0-nfs-mount: Client mount not allowed Expected results: Client mount request should be allowed Steps to Reproduce Case2: ------------------------- 1.gluster volume set <vol_name> nfs.rpc-auth-reject <client1> 2.mount -t nfs -o vers=3 <volume> <mount_point> from client1 Actual results: mount request from client1 allowed. Expected results: Client mount request should not be allowed Additional info:
Created attachment 566999 [details] nfs log when nfs.rpc-auth-allow set
Created attachment 567000 [details] nfs log when nfs.rpc-auth-reject set
*** This bug has been marked as a duplicate of bug 771845 ***