| Summary: | Make keepalive work properly with Cisco PIX/ASA boxes | ||
|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | JS <jakob> |
| Component: | sshd | Assignee: | Assigned to nobody <unassigned-bugs> |
| Status: | CLOSED FIXED | ||
| Severity: | enhancement | CC: | dtucker |
| Priority: | P2 | ||
| Version: | 4.7p1 | ||
| Hardware: | Other | ||
| OS: | Linux | ||
|
Description
JS
2007-12-20 04:31:40 AEDT
Are you using ClientAliveInverval and ClientAliveCountMax (on the server side) or ServerAliveInterval and ClientAliveCountMax (on the client side)? TCPKeepAlive enables the the system-wide TCP keepalive timer on the connection, but that is usually not frequent enough to help with NAT timeouts and the like (~2 hours in many cases). Thanks Darren.
I now have in my client config:
ServerAliveInterval 15
ServerAliveCountMax 10
And on my server:
ClientAliveInterval 15
ClientAliveCountMax 10
This works and my ssh sessions are no-longer disconnected by the Cisco ASA firewall.
You're welcome. Either of ClientAlive* or ServerAlive* is enough to keep your NAT table state fresh, you don't need both (but it's pretty much harmless to have both). Close resolved bugs after release. |