On Fri, 04 Mar 2022, Chuck Lever III wrote: > > 2. NAT > > NAT hasn't been mentioned before, but it is a common > deployment scenario where multiple clients can have the > same hostname and local IP address (a private address such > as 192.168.0.55) but the clients all access the same NFS > server. I can't see how NAT is relevant. Whether or not clients have the same host name seems to be independent of whether or not they access the server through NAT. What am I missing? > > The client's identifier needs to be persistent so that: > > 1. If the server reboots, it can recognize when clients > are re-establishing their lock and open state versus > an unfamiliar creating lock and open state that might > involve files that an existing client has open. The protocol request clients which are re-establishing state to explicitly say "I am re-establishing state" (e.g. CLAIM_PREVIOUS). clients which are creating new state don't make that claim. IF the server maintainer persistent state, then the reboot server needs to use the client identifier to find the persistent state, but that is not importantly different from the more common situation of a server which hasn't rebooted and needs to find the appropriate state. Again - what am I missing? Thanks, NeilBrown
