jetmc / sshtunnel

Automatically exported from code.google.com/p/sshtunnel
GNU General Public License v3.0
0 stars 0 forks source link

Unable to use internet after sshtunnel failed #185

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

Because it happened only once, I'm not sure..
1. Install sshtunnel, setup and activate it
2. It works, so leave it on for several hours
3. Phone goes flat and dies
4. When phone is charged and booted, all port 80 and 443 internet access is 
gone on WIFI only (3G works normally)
5. Reset and Remove menu options did nothing useful
6. Another Reboot did nothing useful
7. sshtunnel refuses to connect
8. iptables, http_proxy, https_proxy settings look normal (unset and clear)
9. removing and re-adding the wifi ap in the wifi settings doesnt help

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

I expect to get the limited browsing allowed by my carrier, on the wireless

What version of the product are you using? On what operating system?

I'm running android 4.3 on a rooted galaxy s3 (UltimaRom v16.0). The sshtunnel 
is the one from the market: 1.5.6

Please provide any additional information below.

Original issue reported on code.google.com by wolfen...@gmail.com on 29 Apr 2014 at 6:02

GoogleCodeExporter commented 9 years ago
Just to be clear, 3G browsing works fine, only wifi browsing is affected

Original comment by wolfen...@gmail.com on 29 Apr 2014 at 6:02

GoogleCodeExporter commented 9 years ago
ok, upgraded to latest version from this website 1.5.5 - no difference.

Original comment by wolfen...@gmail.com on 29 Apr 2014 at 6:39

GoogleCodeExporter commented 9 years ago
ok upgraded to the beta version 2.0.3 - no difference

menu-recover the connection seems to process a bit, but im still unable to 
access the internet at all over wifi (80,443)

Original comment by wolfen...@gmail.com on 29 Apr 2014 at 6:45

GoogleCodeExporter commented 9 years ago
Check your http proxy settings in your wifi config.

Original comment by max.c...@gmail.com on 29 Apr 2014 at 6:48

GoogleCodeExporter commented 9 years ago
ive tried to uninstall and reboot as well, still no joy

Original comment by wolfen...@gmail.com on 29 Apr 2014 at 7:14

GoogleCodeExporter commented 9 years ago
i have checked the wifi config proxy settings, it is set to none. I have 
removed and re-added the settings for the wifi anyway, just in case. nada :(

Original comment by wolfen...@gmail.com on 29 Apr 2014 at 7:14

GoogleCodeExporter commented 9 years ago
things like whatsapp work okay, i assume they run on different ports.. 

Original comment by wolfen...@gmail.com on 29 Apr 2014 at 7:21

GoogleCodeExporter commented 9 years ago
ok, i have determined that the phone is having trouble resolving dns.. 

ping www.google.com
unknown hostname www.google.com

ping 8.8.8.8
64 bytes from 8.8.8.8 in 200ms

Original comment by wolfen...@gmail.com on 29 Apr 2014 at 7:27

GoogleCodeExporter commented 9 years ago
oh sorry false alarm.. that was just because ping on android needs root access:

#busybox ping www.google.com
64 bytes from 173.194.39.51L seq=1 time=134ms

Original comment by wolfen...@gmail.com on 29 Apr 2014 at 7:31

GoogleCodeExporter commented 9 years ago
ok strange, in the command line:

#cd /sdcard
#wget http://www.google.com/index.html
Connecting to www.google.com (173.194.39.50:80)
Connecting to www.google.ae (173.194.39.63:80)
index.html      100%  [***********************] 12975 0:00:00 ETA

So the command line wget can open a website, but the web browsers cannot - like 
chrome

Original comment by wolfen...@gmail.com on 29 Apr 2014 at 7:34

GoogleCodeExporter commented 9 years ago
http://www.google.com/index.html

Chrome: This webpage is not available
Firefox: Server not found
Dolphin: Oops! Web page not available

I wish they would say exactly why they it is failing..

Original comment by wolfen...@gmail.com on 29 Apr 2014 at 7:41

GoogleCodeExporter commented 9 years ago
Ok guys, please help. I donno what else to do/try ?

Original comment by wolfen...@gmail.com on 29 Apr 2014 at 7:58

GoogleCodeExporter commented 9 years ago
ok, so i eventually gave up, formatted my phone and installed another rom. it 
seems to have solved the problem

Original comment by wolfen...@gmail.com on 29 Apr 2014 at 9:54