cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1039
Views
0
Helpful
1
Replies

ASA SSH to outside interface times out

jthunderbird
Level 1
Level 1

Hello everyone,

 

I did search thoroughly for this specific question and could not find an answer. I am sure it is out there somewhere but if someone here could help me out, it would be greatly appreciated.

 

I have numerous ASA 5506-X devices in a hub-and-spoke setup with a 5515-X. They currently all have SSH access over the VPN to their inside interfaces but I also have SSH enabled on the outside interface for a specific IP in case the VPN goes down for some reason. My issue is that if I SSH to any of the devices on the outside interface, it freezes right about the 5 minute mark of idle time.

 

I have checked all the timeout setting and SSH settings and cannot find a setting for this anywhere nor do I know what the setting is. SSH over the VPN works fine. I tried changing the management-interface to outside and it had no effect. Syslog shows nothing when the freeze happens.

 

Is this something obvious I am missing?

1 Accepted Solution

Accepted Solutions

jthunderbird
Level 1
Level 1

This was completely my bad. Turns out the version of putty I was using on my internet-connected box has a bug in it that kills the connection after 5 minutes of idle time. On the VPN side, I was just using my ubuntu cli so did not get the same issue which lead to me believing it had to do with security levels on the ASA.

 

Just in case someone stumbles upon this in a Google search, I was able to fix the issue by navigating to Connection > SSH > Bugs and changing the "Handles SSH-2 key re-exchange badly" from Auto to On.

View solution in original post

1 Reply 1

jthunderbird
Level 1
Level 1

This was completely my bad. Turns out the version of putty I was using on my internet-connected box has a bug in it that kills the connection after 5 minutes of idle time. On the VPN side, I was just using my ubuntu cli so did not get the same issue which lead to me believing it had to do with security levels on the ASA.

 

Just in case someone stumbles upon this in a Google search, I was able to fix the issue by navigating to Connection > SSH > Bugs and changing the "Handles SSH-2 key re-exchange badly" from Auto to On.

Review Cisco Networking for a $25 gift card