Description of problem: I'm not sure whether this is a configuration problem, a bug or valid behaviour. Scenario: Solaris 11 NFS client/Fedora Rawhide NFS server To be exact I'm tyring to run a Solaris Jumpstart server on the Fedora Box. The solaris installer is unable to mount the NFS directory exported by the server. The exact error message is: nfs mount: security mode does not match the server exporting 10.200.255.1:/jumpstart The NFS server per se works, other (Linux) client can mount and access this share. The cause for this seems to be that rpc.mountd does not announce any security flavors in the reply to the mount request package (the field in the package says 'flavors: 0'), and that the solaris client expects at least one to be present (even if it's AUTH_NULL). Who's to blame here? Version-Release number of selected component (if applicable): nfs-utils-1.1.3-6.fc10.i386 How reproducible: Always Steps to Reproduce: 1. Boot solaris installer 2. Try to mount NFS share 3. Actual results: Error message above Expected results: mounted directory Additional info:
This seems to be related to commit 3c1bb23c0379864722e79d19f74c180edcf2c36e. Further version details: The Solaris version I used was release 98. This has been replaced by release 99 by now, it seems, which I have not tested yet.
The same happens from a system installed from Opensolaris 2008.5 (available here: http://dlc.sun.com/osol/opensolaris/2008/05/os200805.iso). It's a live cd, which would make for easy testing.
Thanks... I'll try that...
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
The syntax has changed from /home *(rw,fsid=1,nohide) gss/krb5(rw,fsid=1,nohide) gss/krb5i(rw,fsid=1,nohide) gss/krb5p(rw,fsid=1,nohide) to /home *(rw,fsid=1,nohide,sec=sys:krb5:krb5i:krb5p) see exportfs(5) man page for details
adding sec=sys indeed fixes this.
I am no longer able to reproduce this problem with the latest F-10 or F-11 nfs-utils... So I'm going to close this bug. Please feel free to reopen if the problem comes back... thank you for using Fedora....