jied83 / connectbot

Automatically exported from code.google.com/p/connectbot
Apache License 2.0
0 stars 0 forks source link

Port forwarding works on wifi but not mobile #672

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Establish functioning connection (local port 8080 to localhost:80) on wifi
2. Test that localhost:8080 shows the appropriate webpage.
3. Close connectbot connection
4. Turn off wifi and re-establish connection using mobile data.  
5. Test localhost:8080 and get a "<h4>Error: Host not found or site is down. 
Please check the website address.</h4></body></html>" message.

What is the expected output? What do you see instead?
It's expected that on mobile data that the port be forwarded as usually seen on 
wifi.  The ssh tunnel does get established and there is no indication of an 
error when the mobile data connection is established.

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

What type of system are you trying to connect to?
CentOs 6.4 server.

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

Please provide any additional information below.
All these tests were done on a Nexus 4 with Android 4.3 (nonrooted).
I do see that when I turn on the tethering and connect my Nexus 7 (also Android 
4.3 nonrooted) that I am able to establish the same ssh tunnel and the port 
forwarding works properly.

Original issue reported on code.google.com by kristofo...@gmail.com on 25 Oct 2013 at 2:54

GoogleCodeExporter commented 8 years ago
This became an issue for me when I moved to my LG Google Nexus 5 phone 
(hammerhead) running KitKat. I can no longer create port forwards on Mobile 
networks. 

Original comment by ch...@rennerfamily.org on 11 Mar 2014 at 7:10