Jim Rees wrote: > Here is an old patch I did for adding "nat mode" to openafs. I never put > this in cvs because > > 1) it's part of disconnected afs, and might not be the best way to do this > 2) nat offends me, and increasing network traffic to compensate for lack of > connectivity offends me
With the code that is in the 1.4.1-rc7 file server, this type of patch should no longer be required provided that the client supports UUIDs. For 1.4.0 code was added to the file server to track clients by UUIDs. Unfortunately there was a bug in the code in which the UUID probe was being sent to the wrong connection. As a result, the NAT detection code was never triggered. In 1.4.1-rc7, clients are now tracked by both IP address and port number. When a new connection is established the client is asked for its UUID. If the only thing that has changed is the port number, the data structures are updated, any outstanding callbacks breaks are sent, and the client goes on its merry way. There is still a benefit to maintaining the NAT port mapping but it is no longer required. If the port mapping is maintained, then callback breaks can occur immediately and the user will always see current data. If the NAT port mapping is lost, then the client will only see current data after it next contacts the file server either via a Ping (GetTime or GetCapabilities) or in order to do real work. The UNIX/Linux clients already ping the servers every ten minutes. The Windows clients as of 1.4.1-rc5 do so as well. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
