Result is:
bad inode in call to 9
nfsd: trying to free free inode in nfsxdr.c:470
dev 0805 ino 334588, mode 0100755
nfsd: unauthenticated request from (8d542101:1022)
nfsd: unauthenticated request from (8d542101:1022)
>
> rpcdebug -am nfsd; rpcdebug -am rpc
Hmm, the rpcdebug in linux-nfs-0.4.21 doesn't work because I don't
have a /proc/sys/sunrpc/nfs_debug (with 2.1.33 and nfsd as a module,
nfs client compiled in). BTW the only thing missing in linux-nfs
is a exports(5) manpage.
I can supply tcpdump output if you need it.
>> nfsd: request from insecure port (8d54213b:1077)!
>>
>> Is there a way to allow connections from an "insecure" port?
>
>Yes, export the NFS volume using -o insecure. knfsd supports roughly
>the same set of options as unfsd did.
>
>> IMHO the complete concept of insecure ports should be buried as quickly
>> as possible.
>
>If you write the secure RPC handling and get governments around the
>world to let people import, export and use DES and Diffie-Hellman without
>restriction, I'll do the burying. Port checks are not terribly secure,
>but at least they keep ordinary users from messing around with guessed
>file handles.
On networks with most machines being Windows, Macs and other machines
without a superuser concept it is pretty pointless.
I see that the kernel code in linux-nfs-0.4.19 includes a auth_des
module. Is this module non-functional? It would be very nice to have
an easily compilable kit with the DES code somewhere on a ftp server
in the free world. Then a /sbin/modprobe auth_des would be possible.
-Andi