You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any specific reason why the initial configuration of the devices uses the default ssh timeout ?
If not, could we modify it so it never timeouts? For example on iosv device we could have a exec-timeout 0 under line vty 0 - 4, and later "fix" the setting on as many other devices as possible ?
Yesterday I spent ~4h working with netlab and other tools in parallel working on the bridge not passing traffic on multiaccess links problem and it became tiresome to have sessions timeout and have to reconnect just to issue a ping.
The text was updated successfully, but these errors were encountered:
Is there any specific reason why the initial configuration of the devices uses the default ssh timeout ?
No.
If not, could we modify it so it never timeouts? For example on iosv device we could have a exec-timeout 0 under line vty 0 - 4, and later "fix" the setting on as many other devices as possible ?
That's how I set things up in the old days when I was still working on labs for hours. Please make the changes to the ios.j2 initial configuration template and submit a PR ;)
Is there any specific reason why the initial configuration of the devices uses the default ssh timeout ?
If not, could we modify it so it never timeouts? For example on iosv device we could have a exec-timeout 0 under line vty 0 - 4, and later "fix" the setting on as many other devices as possible ?
Yesterday I spent ~4h working with netlab and other tools in parallel working on the bridge not passing traffic on multiaccess links problem and it became tiresome to have sessions timeout and have to reconnect just to issue a ping.
The text was updated successfully, but these errors were encountered: