kerberos - NFS V4 at FreeBSD hosted, both client and server, mounts OK but there is no read or write on the filesystem, reporting Input/output error -
i have mounted , used nfs version 4 having solaris server , freebsd client. problem when having freebsd server , freebsd client @ version 4. version 3 works excellent.
i use freebsd nfs server since freebsd verson 4.5 (then having ibm aix clients).
the problem: mounts ok, there no principals appear @ kerberos cache, , when trying read or write on mounted filesystem error: input/output error
nfs/server-fqdn@realm , nfs/client-fqdn@realm principals created @ kerberos server , stored @ keytab files @ both sides.
i issue tgt tickets kdc using above both sides root's kerberos cache.
i start services properly: file /etc/rc.conf
rpcbind_enable="yes" gssd_enable="yes" rpc_statd_enable="yes" rpc_lockd_enable="yes" mountd_enable="yes" nfsuserd_enable="yes" nfs_server_enable="yes" nfsv4_server_enable="yes"
then start services @ client: rpcbind, gssd, nfsuserd, @ server above having exports file:
v4: /marble/nfs -sec=krb5:krb5i:krb5p -network 10.20.30.0 -mask 255.255.255.0
i mount:
# mount_nfs -o nfsv4 servername:/ /my/mounted/nfs # # mkdir /my/mounted/nfs/e # mkdir: /my/mounted/nfs/e: input/output error #
same result ls command. klist not show new principals @ root's cache, or other cache. amazing performance @ version 3 love, need local lock files feature of nfs4. second reason security. need kerberised rpc calls (-sec=krbp).
if of has achieved using freebsd server nfs version 4, please give feedback question, i'll glad if do.
comments not give code examples. here setup of freebsd client , freebsd server works me. don't use kerberos if make working minimal configuration can add kerberos afterwards (i believe).
server rc.conf
:
nfs_server_enable="yes" nfs_server_flags="-u -t -n 4" nfsv4_server_enable="yes" nfsuserd_enable="yes" mountd_flags="-r"
server /etc/exports
:
/parent/path1 -mapall=1001:1001 192.168.2.200 /parent/path2 -mapall=1001:1001 192.168.2.200 ... (more shares) v4: /parent/ -sec=sys 192.168.2.200
client rc.conf
:
nfs_client_enable="yes" nfs_client_flags="-n 4" rpc_lockd_enable="yes" rpc_statd_enable="yes"
client fstab
:
192.168.2.100:/path1/ /mnt/path1/ nfs rw,bg,late,failok,nfsv4 0 0 192.168.2.100:/path2/ /mnt/path2/ nfs rw,bg,late,failok,nfsv4 0 0 ... (more shares)
as see client tries mount what's after /parent/
path specified in v4
line on server. 192.168.2.100 server ip , 192.168.2.200 client ip. setup allow 1 client connect server.
i hope haven't missed anything. btw please rise questions on superuser or serverfault rather stackoverflow. surprised question hasn't been closed yet because of ;)
Comments
Post a Comment