Allow option of sending NULL keep-alive packets

kitencx / connectbot

Automatically exported from code.google.com/p/connectbot

Apache License 2.0

0 stars 0 forks source link

Allow option of sending NULL keep-alive packets #60

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Connect to ssh server
2. Switch to other activity
3. Switch back to connectbot

What is the expected output? What do you see instead?
I expect to see the ssh session still live but instead I see connectbot 
reconnecting.

What version of the product are you using? On what operating system?
Latest stable on android on a g1

Please provide any additional information below.

Original issue reported on code.google.com by matthew....@gmail.com on 30 Oct 2008 at 11:55

GoogleCodeExporter commented 9 years ago

I think this happens when the phone goes into low-power mode.  If I'm pinging 
the
phone, it stops cold when the backlight goes off and restarts the second I hit 
the
"menu" key.

W

Original comment by vva...@gmail.com on 31 Oct 2008 at 3:38

GoogleCodeExporter commented 9 years ago

Perhaps, but I get it just from switching to another activity.

Original comment by matthew....@gmail.com on 31 Oct 2008 at 6:22

GoogleCodeExporter commented 9 years ago

cannot replicate in r98 this bug is most likely fixed.

Original comment by not...@gmail.com on 31 Oct 2008 at 8:54

GoogleCodeExporter commented 9 years ago

I think this is mainly an RF issue, but I'll hijack this ticket to add the 
options of
sending SSH NULL packets to keep the TCP session alive.

Original comment by kenny@the-b.org on 3 Nov 2008 at 4:09

Changed title: Allow option of sending NULL keep-alive packets
Changed state: Accepted
Added labels: Type-Enhancement
Removed labels: Type-Defect

GoogleCodeExporter commented 9 years ago

With 1.5.4 I am finding that with edge-only connecting to a remote host and 
switching
applications (Specifically to Touchdown Exchange) results in an almost immediate
disconnect from the remote host.

Switching to WiFi alleviates this issue.

Switching back to Edge-only and reconnecting seems to work fine.

Is there some way to enable verbosity or logging of the connection (aside from 
the
USB/SDK thing)?

Original comment by erikmjac...@gmail.com on 30 Jul 2009 at 2:35

GoogleCodeExporter commented 9 years ago

If you have a working "su" on your device, you can do "su" and then "logcat" in 
the
Local session.

Original comment by kenny@the-b.org on 1 Aug 2009 at 3:07