[OpenAFS] NAT issues resolved - 1.5.17
Christopher D. Clausen
Tue, 3 Apr 2007 17:54:15 -0500
ted creedon <firstname.lastname@example.org> wrote:
> Can anyone describe the final changes?
* Reduce the default UP server probe time from 10 minutes to 5 minutes
to match UNIX. This will not solve the NAT port mapping timeout issue
because most NATs default to a value less that 5 minutes and this value
ensures that the afs client server will start probes 5 minutes after the
last probe set ended. The probe period for any one server is therefore
longer than 5 minutes. The more servers in the list the longer the time
* Before marking a server as down in cm_Analyze, retry the request
using a new rx connection to the server. If the cache manager is behind
a NAT, it is possible that the response from the server is being sent to
the original address:port from which the rx connection was established.
This will appear to the cache manager as the server being down when in
fact it is not. Forcing the use of a new rx connection will result in
the server responding to the most recent address:port assigned to the
client by the NAT.
If the server is in fact down, it will simply take a little longer to