RT-AC68U - ssh - Timeout, server 192.168.1.1 not responding

[vw-kombi]

I did a bit of a search but could not find this mentioned anywhere.
I am new to merlin found out a few things to try - ab-solution, pixelserv-tls, skynet, amtm installed to usb3 32gb formatted as ext2, 512mg swap file added. All seems to be working.
Since doing all this however, the ssh terminal screen times out randomly. I set a ping going also, it also happened. Have I put too much load on this router now ? In addition to the above mentioned add-ons, I have both wifi's going with about 8 direct connections (another access point also), 30 reserved names, adblock level 4, skynet all reccomended (in/out etc).
The router itself stays connected to the internet etc etc, nothing stops working except the ssh session where I would have one of the menu's running (skynet, adblock or amtm).

 

[ColinTaylor]

There's a SSH inactivity timeout on the Administration > System page.

 

[vw-kombi]

Jeez - set to 20, how could I have missed that!
I guess all stuff I have done to date was completed in 20 minutes.......

 

[ColinTaylor]

Bear in mind it's an idle timeout, so you have to type nothing for 20 minutes.

 

[NoSync]

On all of my Asus routers (RT-N66U, RT-AC56U, RT-AC68U, RT-AC86U) SSH connections have always timed out in a few minutes regardless of the idle settings, on all of my wireless clients (Linux, Android, iOS and MacOS) on both bands. I have no clue why, but I stopped worrying about it long ago. [emoji4]

 

[RMerlin]

On all of my Asus routers (RT-N66U, RT-AC56U, RT-AC68U, RT-AC86U) SSH connections have always timed out in a few minutes regardless of the idle settings, on all of my wireless clients (Linux, Android, iOS and MacOS) on both bands. I have no clue why, but I stopped worrying about it long ago. [emoji4]

I frequently have SSH sessions opened for a few hours here while doing development without any issue. Check your SSH client, most offer a setting called "keep alive".

 

[NoSync]

I frequently have SSH sessions opened for a few hours here while doing development without any issue. Check your SSH client, most offer a setting called "keep alive".

Yep, when I really need the connection to stay up I just open a ping session; keepalive settings are basically the equivalent, but there should be no need for that with a properly set timeout period. In any case, screen/byobu are my friends, so I can live with that (although I could never figure out the root cause). Most of the times, unless I do what I mentioned, my sessions do not survive being inactive more than 2/3 minutes.

 

[XIII]

Maybe mosh can help?

(seems to finally work for me)