Bug#644948: nfs-common: Wrong uid/gid with latest version using NFSv4
Anders Boström wrote:
> Sorry for the late respons... I've got time to test this again, and it
> is indeed a domain-problem. However, I don't get any nfsidmap-messages
> in the client syslog, but I do in the server. If I reconfigure my
> client idmapd.conf to 'Domain = localdomain' it works as expected. If
> I use the default idmapd.conf from nfs-common 1:1.2.5-2+b1 it does not
> work.
>
> The server is in this case using the default idmapd.conf from
> nfs-common 1:1.2.2-4. And doing any change on the server regarding the
> domain-configuration will break a lot of clients, all running NFSv4
> using Debian stable, Ubuntu etc. Soo it is a no-go.
>
> Also I don't understand how I'm supposed to configure this. I have
> another client in another domain. It is supposed to mount NFS
> from it's own domain *and* from our server. If 'Domain = localdomain'
> is configured in all places, it works, but I how is this
> supposed to be configured???
No, unfortunately, Domain = localdomain was just bad default that got
shipped. Your server and its working clients are currently relying on
what is essentially a misconfiguration. Domain should be set to your
NFSv4 Domain Name. See RFC3530 section 5.8, or RFC5661 section 5.9.
Multi-domain NFSv4 is still in draft:
http://tools.ietf.org/html/draft-adamson-nfsv4-multi-domain-access-04
--
Jamie Heilman http://audible.transient.net/~jamie/
"...thats the metaphorical equivalent of flopping your wedding tackle
into a lion's mouth and flicking his lovespuds with a wet towel, pure
insanity..." -Rimmer
Reply to: