Open GoogleCodeExporter opened 9 years ago
Same issue on my T889 Note 2
Original comment by gary.pa...@gmail.com
on 15 Apr 2013 at 6:17
Same issue on galaxy s3
Original comment by Itako.Mi...@gmail.com
on 9 May 2013 at 10:32
Same issue on GS3 with Cyanogen Mod running
SSHTunnel Version: 1.5.6
CyanogenMod Version: 10.1-20130516-Nightly-d2spr
Android Version: 4.2.2
Original comment by neoinu1
on 23 May 2013 at 8:28
Interesting. So far that is 3 different samsung devices all on different roms
including stock.
Original comment by wayne.ne...@gmail.com
on 23 May 2013 at 8:30
Same issue with an older AT&T ZTE Z990 Avail, custom ROM, rooted.
ALL WiFi tether apps have this same issue:
Either no connection at all, or it shows the carriers IP, not the ssh servers
IP.
Same result whether I start the tunnel first, then the WiFi Tether app, or the
WiFi Tether, then the Tunnel.
Basically, WiFi Tehther is not using the Tunnel proxy.
Original comment by cwwilson...@gmail.com
on 16 Jun 2013 at 8:43
What if you tether before starting the tunnel? It may be that they are each
re-writing the IP tables, and the last one to do so should be the tunnel to get
the correct routing.
Original comment by DeathByL...@gmail.com
on 13 Sep 2013 at 5:11
Unfortunately it yields the same results. What I havent tried , but will
shortly , is start a tethering session before the data is actually connected.
Its odd though that all other apps are tunneling properly. So far the only work
around Ive found, is to use SSHtunnel on the client connecting to the phone (
also an android device ), or use SSH directly on the desktop. Its a shame we
cant grab all packets on the phone and redirect them. It would certainly be
more secure if on a public Wifi connection as well as keep the carriers prying
eyes out of our data.
I might just have to set up a VPN vs using my already in place ssh server :(
Also, if it were working correctly, we would be able to connect PS3 / XBOX / or
any other device directly to the phone. Certainly an added bonus.
Original comment by wayne.ne...@gmail.com
on 13 Sep 2013 at 5:20
Agreed, it should definitely work that way. I'm guessing that the tethering app
is the only one working because it's the only other one that re-writes IP
tables, but that's just a guess.
Has anyone tried this with the new beta version? I assume it probably does the
same thing =(
Original comment by DeathByL...@gmail.com
on 13 Sep 2013 at 5:32
[deleted comment]
Manually configuring the proxy on the laptop seems to resolve this. My phone
(GT-i9300 SGS3 International running CM10.2) is getting an ip address (for
tethering) of 172.16.11.254, so i set the proxy to that address, use the local
port listed in SSH Tunnel, and now traffic from the laptop is correctly
displaying as coming from the remote proxy. Still troubleshooting this on my
PS3, though (which is the entire point, since t-mobile is blocking everything
except my linux laptop, with or without the proxy).
Original comment by rob.kle...@gmail.com
on 18 Jul 2014 at 5:41
Original issue reported on code.google.com by
wayne.ne...@gmail.com
on 21 Mar 2013 at 5:46