it only lets me connect to google.com no other website

[GoogleCodeExporter]

Htc evo 3d

2.3.3

WiFi Tether for Root Users 3.1-beta2 

its works super fast but only on google no other plz update the version fix 
that bug

Original issue reported on code.google.com by juanserg...@gmail.com on 19 Jul 2011 at 10:25

[GoogleCodeExporter]

Ahm. That can't be an app-bug. It simply makes no sense to me that it's only 
working for google-sites.

Is domain-name translation working?

Open a command-prompt on your pc and type:

nslookup microsoft.com 8.8.8.8

or

nslookup facebook.com 8.8.8.8

Does this return valid results?

Original comment by harald....@gmail.com on 20 Jul 2011 at 9:41

[GoogleCodeExporter]

it doesent bring back results only on google.com 

Original comment by juanserg...@gmail.com on 20 Jul 2011 at 10:47

[GoogleCodeExporter]

Same problem with Motorola Triumph.
All google sites are fine including youtube, but TCP slow respond or no respond 
for non-google sites(http)... I don't know why FTP and iPhone weather/stock 
works.
DNS works fine.

Original comment by legendm...@gmail.com on 21 Jul 2011 at 9:25

[GoogleCodeExporter]

I'm having this same issue.  Google sites work great! But non-google sites 
don't even want to load.  I tried nslookup and received the following results:

DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  192.168.3.254

DNS request timed out.
    timeout was 2 seconds.
Name:    google.com
Addresses:  74.125.127.99
      74.125.127.103
      74.125.127.106
      74.125.127.147
      74.125.127.104
      74.125.127.105

Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Name:    google.com
Addresses:  74.125.127.105
      74.125.127.104
      74.125.127.147
      74.125.127.106
      74.125.127.103
      74.125.127.99

Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Name:    facebook.com
Addresses:  69.63.189.16
      69.63.189.11
      69.63.181.12

Original comment by cfry...@gmail.com on 24 Jul 2011 at 9:51

[GoogleCodeExporter]

I too am having this same issue with my Evo 3d. I have noticed though, that 
addresses that go to a port other than 80 go through just fine. I have my 
router set to use an external port other than 80 to forward http requests to my 
web server on my computer, and I am able to access it using wifi-tether.

Original comment by rubikscu...@gmail.com on 25 Jul 2011 at 12:11

[GoogleCodeExporter]

 How can this idea work for phone connections through 3g or 4g?

Original comment by cfry...@gmail.com on 25 Jul 2011 at 2:39

[GoogleCodeExporter]

I'm not sure how feasible it would be to have to port forward all internet 
connections going through a phone, I was just pointing out that it was working 
with that specific web address. 

I did find something interesting though, when I changed the radio to 4g and 
tried tethering, it worked perfectly and I was able to access any site. I don't 
know what would be different between 3g and 4g which would cause that, but for 
anybody in a 4g market I think it is an acceptable work-around for the time 
being.

Original comment by rubikscu...@gmail.com on 25 Jul 2011 at 3:12

[GoogleCodeExporter]

The android world seems to be full of those fixes.  Thanks!

Original comment by cfry...@gmail.com on 25 Jul 2011 at 3:50

[GoogleCodeExporter]

I'm having this issue as well.  I've tried several different versions of WiFi 
Tether including 3.1 Beta 2 and have tried many configurations of the 
application all with the same results.  I tried with the original temporary 
root method and also with the new Revolutionary S-OFF and permanent root.  No 
matter what I try I can get to any Google site but no other sites.  I would be 
happy to perform any troubleshooting or provide logs that may help.  Thanks!

Original comment by brian.co...@gmail.com on 30 Jul 2011 at 3:50

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The fix for this seems to be to start then stop Barnacle, then start Wifi 
Tether. Something Barnacle is doing is letting me browse non-Google sites.

Original comment by jrgut...@gmail.com on 31 Jul 2011 at 5:38

[GoogleCodeExporter]

Barnacle didn't work, but turning Barnacle on then off fixed the Wifi Teather 
problem!  Outstanding!

Original comment by cfry...@gmail.com on 31 Jul 2011 at 3:08

[GoogleCodeExporter]

Barnacle works fine for me. Even if turning it on and off allows this app to 
work, what's the point? Why not just use Barnacle instead of having the extra 
step? 

Original comment by brian.co...@gmail.com on 31 Jul 2011 at 3:13

[GoogleCodeExporter]

IDK, maybe the developers here can use this information to fix the problem with 
some of our phones...

Original comment by cfry...@gmail.com on 31 Jul 2011 at 5:39

[GoogleCodeExporter]

Wired and Wireless tether for root users only works on 4g for me, which is 
fine, but I'd hope they fix it for 3g. It connects, but I cannot get to any 
websites on 3G

Original comment by moulton....@gmail.com on 1 Aug 2011 at 3:38

[GoogleCodeExporter]

Could you guys please try to change the dns-servers like described here:
http://code.google.com/p/android-wifi-tether/issues/detail?id=1020#c2

Thanks!

Original comment by harald....@gmail.com on 2 Aug 2011 at 9:43

[GoogleCodeExporter]

Anyone?

Original comment by harald....@gmail.com on 4 Aug 2011 at 1:18

[GoogleCodeExporter]

The DNS servers, once changed from google's DNS servers to any of a number of 
DNS servers (just google, 'DNS Server List'), and the Wifi Tether works great.  
Thanx!

Original comment by cfry...@gmail.com on 5 Aug 2011 at 3:44

[GoogleCodeExporter]

really? mmmh.

could you please try:
208.67.222.222 
208.67.220.220

these are from opendns.com - if they work i make them default.

thanks.

Original comment by harald....@gmail.com on 5 Aug 2011 at 9:06

[GoogleCodeExporter]

Changing the DNS servers to 208.67.222.222 and 208.67.220.220 didn't help.  I 
can still only get to Google sites with WiFi-Tether and Barnacle still works 
for every site I've tried.

Original comment by brian.co...@gmail.com on 5 Aug 2011 at 1:27

[GoogleCodeExporter]

Wifi tethering is also not working for me for sites other than Google.  I have 
tried both verion 3.0-pre14 and the 3.1-beta2.  I have the EVO 3D.  I rooted 
recently, no specific ROMs installed.  I have also tried the DNS servers you 
listed: 208.67.222.222 and 208.67.220.220.  Thanks for the great work!  I would 
love to continue using your Wifi Tether, if possible.

Original comment by klee...@gmail.com on 7 Aug 2011 at 1:18

[GoogleCodeExporter]

This is quite a peculiar problem...

Original comment by blaken2...@live.com on 7 Aug 2011 at 1:43

[GoogleCodeExporter]

See post #18. Changing the dns seems to solve this problem.

Please try some other nameservers:
http://www.tech-faq.com/public-dns-servers.html

Original comment by harald....@gmail.com on 8 Aug 2011 at 8:27

[GoogleCodeExporter]

Changing DNS gives no joy for me. On an Evo 3d with 3.1 beta 2 only starting 
and stoping barnacle gives me a connection to non google sites.

Original comment by skull...@gmail.com on 9 Aug 2011 at 9:39

[GoogleCodeExporter]

Lol, found out I could also browse .eu sites, weird.

Original comment by skull...@gmail.com on 9 Aug 2011 at 9:44

[GoogleCodeExporter]

Is anyone that is having this issue on a custom rom? Im stock and rooted myself.

Original comment by skull...@gmail.com on 9 Aug 2011 at 9:52

[GoogleCodeExporter]

I have Evo 3D, rooted using Revolutionary, no custom ROM, kernel version 
2.6.35.10-gcb1cf83, Android 2.3.3. I only have 3g network in my area. WiFi 
Tether for Root Users 3.1-beta2 

I too could only access google sites, and once or twice other sites (clorox 
handi-wipes loaded LOL) but I use my wifi tether as my only internet access, 
and I maintain 4 websites, I could not get any of them to load. Couldn't get 
facebook to load, etc. 

I tried changing the DNS settings as described here. Tried CMD/nslookup as 
described here and it timed out... nothing worked. Installed Barnacle and that 
application works fine. For now I'm going to keep using Barnacle. I do like the 
Wi-Fi Tether for Root Users interface better, so I'll come back and try it 
again.

One thing, on the download page it says "This application requires a 
"rooted"-device and(probably) a custom-kernel which supports netfilter 
(iptables)! Please see the FAQ for detailed information." I don't know if I had 
that custom kernel as mentioned, and I couldn't find any info on your FAQ page 
to help me discover what I had and/or what I needed/how to get it. So that may 
be the issue.

A little more feedback...
- The hide SSID option does not work.
- For some reason the WEP security option does not work, so I have to run it as 
an unsecured network, however, access control still works. It's just annoying 
seeing someone try to log on constantly. I wish there were an option to 
dis-allow access and boot the ID from ever trying to access again, or hide the 
ID after it's been disallowed. (does that make sense?)

Original comment by virtuall...@gmail.com on 15 Aug 2011 at 4:31

[GoogleCodeExporter]

I think I have found the fix for this issue.

I did some google searching and found some past issues similar to this with 
non-Android linux users. Exact same symptoms. Able to access google and a few 
other sites and no others. In each case it was a MTU issue which was resolved 
by applying MSS clamping. I tried enabling the MSS clamping option, but it 
didn't help the situation.

I loaded the Sprint Hotspot application, which does work, and took a look at 
the iptables rules being used. I then compared them to the Wifi Tether iptables 
rules. The difference is that the Sprint Hotspot app applies MSS clamping in 
the FORWARD chain of the filter table and Wifi Tether applies it in the mangle 
table.

I edited the tether.edify rule to apply MSS clamping in the FORWARD chain of 
the filter table and Wifi Tether started to work properly.

I am attaching the modified tether.edify file. The only line I changed was the 
one which applies the MSS clamping option.

Original comment by sedlme...@gmail.com on 16 Aug 2011 at 3:34

Attachments:

• tether_edify

[GoogleCodeExporter]

I have attached an updated tether.edify which now also removes the section 
which flush the MSS clamping rules from the mangle table. With the MSS clamping 
rule moved to the FORWARD chain of the filter table the MSS clamping rules get 
flushed when this chain gets flushed earlier in the script.

There is also a change regarding launching of the Routing fix on some Evo 3D 
ROMs. On some ROMs the fixroute.sh was being launched but having no affect. I 
changed the run_program command to have fixroute.sh launched using exec and it 
now proper launches and runs on all ROMs I've tested on.

Original comment by sedlme...@gmail.com on 17 Aug 2011 at 6:14

Attachments:

• tether.edify

[GoogleCodeExporter]

@sedlme...@gmail.com: Wow. Thank you! That really helps. Will quickly put a new 
beta together which will include you changes!

Thanks!

Original comment by harald....@gmail.com on 17 Aug 2011 at 8:36

[GoogleCodeExporter]

Original comment by harald....@gmail.com on 17 Aug 2011 at 8:38

• Changed state: Started
• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

beta3 is here:
http://android-wifi-tether.googlecode.com/files/wifi_tether_v3_1-beta3.apk

Hope this issue is solved now :-) - don't forget to enable MSS clamping in 
settings.
(MSS clamping is removed from settings if your kernel does not support this 
feature.)

Original comment by harald....@gmail.com on 17 Aug 2011 at 11:54

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

And ... if that does not work. Try to set the mtu-size manually:

adb shell
su
setprop persist.data_netmgrd_mtu 1500

Let me know what works for you guys.

Original comment by harald....@gmail.com on 18 Aug 2011 at 12:13

[GoogleCodeExporter]

Beta 3 works for me.  I could only try on 3G but I was able to get to every 
non-Google site I tried.  Thank you!

Original comment by brian.co...@gmail.com on 18 Aug 2011 at 3:53

[GoogleCodeExporter]

Issue 1057 has been merged into this issue.

Original comment by harald....@gmail.com on 18 Aug 2011 at 9:05

[GoogleCodeExporter]

Issue 1058 has been merged into this issue.

Original comment by harald....@gmail.com on 18 Aug 2011 at 9:06

[GoogleCodeExporter]

Issue 1082 has been merged into this issue.

Original comment by harald....@gmail.com on 19 Aug 2011 at 7:13

[GoogleCodeExporter]

Beta 3 did fix all the issues with the Android 2.3.3 version on the Evo 3D.  
Yesterday, however, HTC released 2.3.4 for the 3D (HTC version 2.08.651.2).  
Since then, wifi tether has stopped working on 4G but is still working on 3G.  
On 4G, my laptop connects and even receives an IP address, but it does not have 
internet access.  Both HTC routing fix and MSS clamping are checked, just as 
before the HTC update.  In fact, ALL the settings are the same as they were 
before the update.  

To summarize: updating the Evo 3D to 2.3.4 (as of yesterday) broke wifi tether 
3.1-beta3 on 4G but not on 3G.  The wifi tether settings are the same they were 
with Android version 2.3.3 when wifi tether worked fine on both 4G and 3G.

Original comment by gageorga...@gmail.com on 19 Aug 2011 at 8:50

[GoogleCodeExporter]

YES, with Beta 3 and MSS Clamping (HTC EVO 3D Android 2.3.4) I was able to get 
on xbox live. But I LIVE, WORK, and PLAY in areas with at least 1 bar of 4G. 
Which is WAY faster than 3G. So hopefully we get a fix soon!

Original comment by wwjoshdew on 19 Aug 2011 at 1:17

[GoogleCodeExporter]

Ok,the issue with the EVO 3D Android 2.3.4 is that the interface name changed 
when using 4G. Previously the network interface was named rmnet0 whether on 3G 
or 4G. Now when on 4G the interface name is wimax0. 

Original comment by sedlme...@gmail.com on 19 Aug 2011 at 3:13

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

great work.   Evo 3d running latest ota with Android 2.3.4... 3g works... 
unable to test 4g.

Original comment by mark.gas...@gmail.com on 19 Aug 2011 at 3:41

[GoogleCodeExporter]

Ok, besides the interface changing to wimax0 for 4G the routing table changes 
from gprs to wimax. The fixrouting.sh script is going to need to be updated to 
account for these changes.

Original comment by sedlme...@gmail.com on 19 Aug 2011 at 5:34

[GoogleCodeExporter]

Ok. Let's try ...
http://android-wifi-tether.googlecode.com/files/wifi_tether_v3_1-beta4.apk

I've modified the fixrouting-script. I don't have such a phone available for 
testing. So ... any feedback is highly appreciated!

Thanks.

Original comment by harald....@gmail.com on 19 Aug 2011 at 9:03

[GoogleCodeExporter]

I just downloaded and will try it out. If your fixed script doesn't work 
attached is one I just finished putting together and testing. 

I however substantially changed the existing script because it hurt my head 
with all the case statements and redirection of output in the middle of the 
script.

Original comment by sedlme...@gmail.com on 19 Aug 2011 at 9:08

Attachments:

• fixroute.sh

[GoogleCodeExporter]

YAY! HTC EVO 3D is in the list now! Harald you are AWESOME! I swear to god I am 
donating ASAP! I get a couple nice deposits before the 1st of September and I 
am gonna donate! Unfortunately my apartment is 3 stories high and I live on the 
first floor, partially underground (stays pretty cool!) so I can't test 4G! BUT 
I will ASAP! Here in Kansas City We get a good 4G signal when I'm not at home.

Original comment by wwjosh...@ymail.com on 19 Aug 2011 at 9:10

[GoogleCodeExporter]

Well. I simply duplicated the existing section for the gprs-table. Just 
something to test.

Original comment by harald....@gmail.com on 19 Aug 2011 at 9:15

[GoogleCodeExporter]

And by the way ... if I remember correctly ... the redirect of output was 
needed because of the limited stock-shell (you have busybox installed?).

But yeah. The number of case statements could be reduced. Anyway. I can't 
modify something (which is known to be working) if I'm not able to test it.

Original comment by harald....@gmail.com on 19 Aug 2011 at 9:27

[GoogleCodeExporter]

I can confirm that the beta4 works on the Evo 3D with 2.3.4 on both 3G and 4G.  
Fantastic work Harald and sedlme!  Thanks a bunch.

Original comment by gageorga...@gmail.com on 19 Aug 2011 at 9:34