Forwarding does not work on Motorola Droid

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Tap menu, select port forwards
2. Tap menu, Add port forwards
3. Fill in the dialog (or leave defaults) and press Create port forward

What is the expected output? What do you see instead?

I would have expected an entry to appear on the screen that indicated the
port forward that was just created. Instead, nothing appears and the
forward does not become active.

What version of the product are you using (you can see this by using Menu
-> About in the Host List)?

1.5.5 (r409 1009.09.06)

What type of system are you trying to connect to?

Centos 4. Note shh connection is established (using public key)

If you are able to connect, what is the output of "echo $TERM", "uname -a",
and any other relevant information on the host?

TERM=screen
uname -a
Linux timone 2.6.20.4jmc #2 SMP PREEMPT Wed Mar 28 00:01:22 EDT 2007 i686
i686 i386 GNU/Linux

Please provide any additional information below.

Original issue reported on code.google.com by jeffcr...@gmail.com on 11 Nov 2009 at 3:32

[GoogleCodeExporter]

Still present with svn r427 version

Original comment by jeffcr...@gmail.com on 21 Nov 2009 at 9:36

[GoogleCodeExporter]

I'm having problems with this on my Droid as well. After successfully 
connecting via
SSH, there is a brief message displayed that looks like confirmation of the 
forwarded
port but the screen clears too quickly to be read. When attempting to use that 
port
via the phone's browser (http://localhost:1234) no connection is established.

Original comment by diskcras...@gmail.com on 6 Jan 2010 at 10:08

[GoogleCodeExporter]

Port forwards work fine on my moto Droid, It seems (from my research on a 
non-rooted 
phone) that the device automatically rejects any localhost requests to 
well-known 
TCP ports.  My HTTP service port needed to be changed from port 80 as it is 
configured on my PC because it would not connect.  Same with port 21 for FTP.

I have successfully forwarded HTTP, Remote Desktop, Telnet, and FTP-C/FTP-D on 
my 
phone by using higher TCP ports.  The Client Dynamic tunnel feature even works 
well, 
I can turn the forwarding off and on without re-connecting the client to the 
server.

Original comment by mericks...@gmail.com on 14 Jan 2010 at 5:25

[GoogleCodeExporter]

I see the same problem with my htc Droid Eris, running connectbot
1.6.1.  I can establish an ssh connection to a Linux box running
Fedora Core 12. Then I can go through the dialog which ought to forward
local port 8080 to localhost:80 on the remote machine.  When I click on
"create port forward", nothing appears on the screen and I am not able
to connect with local port 8080, which ought to have been forwarded to
port 80 on the remote host.

   Nickname:    xxx
   Type:        Local
   Source port: 8080
   Destination: localhost:80

Original comment by vincild...@gmail.com on 22 Jan 2010 at 12:36

[GoogleCodeExporter]

I'm having this issue with the Motorola Milestone in the UK. The Server is 
running
Ubuntu 9.10 with Webmin/Sabnzbd/Transmission. The main ssh shell session 
connectes
and I can run commands without a proble. However I have three port forwards 
operational.

The UI shows the port forwards as being connected but in the browser things just
timeout without the pages loading completely. 

10000:localhost:10000 - Webmin (https://localhost:10000)

On this one, it gives the certificate warning then just hangs at the 10% progess
until it timeout with a "data connectivity error"

10001:localhost:10001 - sabnzbd (http://localhost:10001/sabnzbd)
10002:localhost:10002 - transmission (http://localhost:10002)

The progress bar goes about 10-20% then stops, I've had about a 5% success 
getting
the transmission page to load but its very slow and timeout if I refresh. The 
sabnzbd
page loads eventually but is missing all of the css/theming.

I've also tried this config with a jailbroken iphone and open ssl with no 
problems
and locally behind my firewall without ssl and all pages load fine so its not a
server/browser issue.

Original comment by kateuk...@gmail.com on 26 Jan 2010 at 2:42

[GoogleCodeExporter]

Just checked with the latest trunk build (revision 466) and the connectivity is 
still
an issue on the milestone for forwarded ports

Original comment by kateuk...@gmail.com on 26 Jan 2010 at 4:31

[GoogleCodeExporter]

If you could get a logcat of what's going on when this happens, that would be 
great.
Have you tried enabling compression on the SSH connection?

Original comment by kenny@the-b.org on 12 Feb 2010 at 5:06

[GoogleCodeExporter]

I think I have figured out my problem with port forwarding on
the Droid Eris.  I think it's a combination of user error
and some aspects of the user interface that invite confusion.

After I establish an ssh connection, I want to set up a port forward.
I press "menu" then click on "Add port forward", and see a form like this:

   Nickname: Internal Webserver
   Type: Local
   Source port: 8080
   Destination: localhost:80

The Nickname, Source port and Destination fields are all in a light
grey print.  (That might have been a clue.)

These appeared to be default settings which have already been
filled in.   Since they were the values I wanted to use, I just clicked
on "Create port forward", without typing anything in those fields.
Nothing happened: no port forwarding setup, but no error dialog either.

Looking at the debugging log with adb, I found a Java stack trace with:

   "Could not update port forward" and

   "ConnectBot.PortForwardListActivity(22148):
   java.lang.NumberFormatException:
   unable to parse '' as integer"

That suggested that the values I saw in light grey were not actually
being entered in the forms, but were simply hints to the user showing
what sort of things to enter.  I was actually submitting blank fields.
The difference between a grey hint and a solid black data entry is
pretty subtle.

When I type explicit values into those fields, I am now able to set up a port
forward. 

So the functionality seems to work, but I'd like to suggest a couple of
changes to the user interface.

First, it would be convenient if the values which appear in those fields
were not just hints, but actual default values.  Why not, since they
are useful defaults?

Two, it would be nice to see an explicit error message telling me what
was wrong with the values I entered in the form, and what was expected.
My experience suggests that this will be a common error until
the user learns that the values displayed
in the form are not pre-populated default values.

Thanks for this very useful application.  With port forwarding, I am
now a happy user.

Original comment by vincild...@gmail.com on 15 Feb 2010 at 4:44

[GoogleCodeExporter]

I agree with vincildea. Both the defaults and some explicit entries appear to 
end up
with the no action taken, no error on the part of the interface. The result is 
that
especially for a user that has never seen a successful port forward, one is left
wondering if perhaps it was accepted since there is no experience with seeing 
what a
successful add looks like.

Original comment by jeffcr...@gmail.com on 15 Feb 2010 at 12:12

[GoogleCodeExporter]

My port forwarding looked successful until I looked at the list of forwarded 
ports
and saw that it had a line through it. No indication as to why.

Original comment by diskcras...@gmail.com on 15 Feb 2010 at 11:49

[GoogleCodeExporter]

After reading comment #8 and trying again, I think the problem has been 
identified. I
too assumed the displayed default values were just that--default values. 
Manually
entering a value in each input box resulted in a successful port forward. Please
revise this portion of the UI!

Original comment by diskcras...@gmail.com on 17 Feb 2010 at 3:20

[GoogleCodeExporter]

Motorola Droid, showing the same problems as comment #5. I have "androidVNC" 
and it
works through the forward, but my two other forwards 10000->local:10000 and
80->local:29000 give timeout/communication errors("web page not available"). 
Tried
using "localhost" and "127.0.0.1" in url blank, and downloaded "dolphin" and 
"coco"
browsers. Both had the same problems.
The vnc forward is the first in the list, and is 5901 -> local:5901. I have 
tested
all of these connections using a desktop client.
Server: Linux hal9000 2.6.31-19-generic #56-Ubuntu SMP Thu Jan 28 02:39:34 UTC 
2010
x86_64 GNU/Linux
Client: Connectbot 1.6.2 (r480 2010.02.12)

Original comment by h4mm3...@gmail.com on 11 Mar 2010 at 12:51

[GoogleCodeExporter]

Motorola Droid 2.1, Connectbot 1.6.2, Ubuntu 9.10

Forwarding -L 5901:localhost:5901 works flawlessly with androidVNC.

However, forwarding -L 8080:localhost:80 with the android (or any other) 
browser only
works sporadically and I'm having trouble reproducing the problem reliably. 
Sometimes this port forward works as it should, and all http content/css is
transferred (this is about 10% of the time).

On the other hand, sometimes, css content will drop out or I do not even have a
connection/timeout as described by karteuk (#5) and h3mm3rjw (#12).  When this
happens, the ssh connection also freezes (which kills the other port forward). 
Sometimes, manually disconnecting the ssh session frees up the used ports, 
sometimes
it doesn't and only killing the Connectbot process frees the ports so that a 
new ssh
session can be started.  Rebooting doesn't seem to make a difference.

Any ideas out there?  Is there any way this is related to the android browser? 
(Don't get me started on untrusted ssl certs...)  Or something related to the 3G
connection?  Now I'm grasping at straws...

Original comment by abigale....@gmail.com on 17 Apr 2010 at 6:47

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I posted a new issue in this regard (I think it was issue 347 but hasn't showed 
up yet).  It seems that connectbot may not be reliable over Verizon 3G, while 
it works fine with a wifi connection.  ssh shell is unreliable without 
compression turned on, and a VNC port forwarded tunnel connects but then times 
out.  Again both work fine over wifi.

Original comment by jlk332...@gmail.com on 29 Aug 2010 at 6:55

[GoogleCodeExporter]

I have this problem as well connecting to a router running tomato.  Almost 
always the http requests fail (timeout).   This is when running on a wifi 
connection.

Ran aLogcat, but did not see anything worrysome.

Original comment by ericraym...@gmail.com on 2 Sep 2010 at 9:59

[GoogleCodeExporter]

Resolution regarding comment 15 posted by me.  
The problem was my broadband router.  I have a qwest broadband IP router. It's 
an Actiontec M1000.  The broadband router was simply buggy and dropped 
returning packets (data flowing back to the Droid from my server).  I never had 
a problem with it going out from my home.  Anyway, others had similar problems 
and put the interface into bridge mode to resolve. This worked for me.  
Connectbot ssh and port forwarding tunneling now works great from my Droid to 
my home servers.

Original comment by jlk332...@gmail.com on 5 Sep 2010 at 8:05

[GoogleCodeExporter]

Dude, I spent 4 hours trying to figure out the problem and finally found 
vincildean comment which fixed it.

The UI seriously need to be fixed, either that or actually default 8080 and let 
user change it if they need

Original comment by yeecho...@gmail.com on 7 Nov 2010 at 12:26

[GoogleCodeExporter]

Hi there, i ve a Moto Defy with Android 2.2.1 (PAYS ROM), Connectbot 1.7.1. 
(v1.7.1.2010.10.08) and my carrirer is "Telecom Personal" from Argentina.

The issue im having its that i use the connectbot to establish ssh2 connection 
and then a tunnel inside it to check mails.

When i do it with a wi-fi network, all goes ok, but when i do it on 3G network, 
i can connect to SSH but cant stablish tunnels.
So, i try forcing APN to use only 3G network but still not working.
Ive test MTU size on wifi and on 3g and its the same on both (1500)
Additionally i ve convert my droid into an access point and connect via my 
laptop to the ssh server and create tunnels without any problem, so, it seams 
that my carrier isnt blocking.

Any help?

Original comment by agust...@gmail.com on 4 May 2011 at 1:55