The keep-alive pings are sent from the client. Only the client can maintain the NAT's port mapping. Windows clients older than 1.4.1-rc5 ping the servers once every hour; 1.4.1-rc5 and later ping every ten minutes just like the UNIX/Linux clients.
Jeffrey Altman ted creedon wrote: > The windows client stays connected more reliably thru 2 NATTED firewalls > than the Linux client. If the Linux client were upgraded to do whatever the > windows client does the "cellname workaround" would be acceptable. > > Connectionless UDP packets are port forwarded to the Class C server. I > recall previous mailings suggesting changing the timeout on the at the > firewalls. > > That being said, is it possible for the server to reply with a keep alive > no-op? > > tedc > -----Original Message----- > From: Derek Atkins [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 14, 2006 6:49 AM > To: [EMAIL PROTECTED] > Cc: [email protected] > Subject: Re: [OpenAFS] Connection timeouts > > "ted creedon" <[EMAIL PROTECTED]> writes: > >> For a client/server combination each behind a firewall: >> >> 1. Why does the Linux client timeout fairly rapidly requiring a client >> restart? > > NAT UDP Timeouts. The firewall/NAT gateway loses the UDP mapping > between the client and the server.. The server can no longer talk > to the client.. Callbacks fail.. The server marks the client as > "Bad" because it can't talk back to the client. > > -derek
smime.p7s
Description: S/MIME Cryptographic Signature
