Hi All, I was seeing timeout errors with my OpenAFS client. I have OpenAFS client from a RHEL 5.5 in a VMware image, where the IP is NATted. The VMware Player tool comes with a network configuration utility, using which I set up UDP timeout for NAT to "0" that would mean to not timeout.
The problem as I understand is after timeout value the port number NAT mapping for the virtual OS image is not maintained and when the file server tries to send responses to the port where it was sending earlier, the OpenAFS client is not able to get it, as the earlier port mapping is gone. This is working pretty good for me, if you have similar configuation you may try this out. -- Avinesh Kumar On Fri, May 6, 2011 at 11:29 PM, Jeffrey Altman < [email protected]> wrote: > On 5/6/2011 7:10 AM, Jaap Winius wrote: > > Quoting Jeffrey Altman <[email protected]>: > > > >> 10 to 15 minutes is more than sufficient. > > > > Since ip_conntrack_udp_timeout and ip_conntrack_udp_timeout_stream were > > decreased from 28800 to 900 seconds, I've been seeing lots of dropped > > packets again. Any explanations? I've now increased both values to 3600. > > > > Cheers, > > > > Jaap > > Which party is behind the NAT? Server or Client? > > >
