Open GoogleCodeExporter opened 9 years ago
Apparently, after looking into this further, it has something to do with
sprint's redirection of dns requests. It doesn't sound like there's
necessarily any good [easy] way around this. Would love to hear if anyone
knows of one.
Original comment by jctrump
on 17 Apr 2011 at 10:03
Please try beta version 3.0-pre13 available here:
http://code.google.com/p/android-wifi-tether/downloads/list
This one lets you change the dns-servers to your needs.
Original comment by harald....@gmail.com
on 18 Apr 2011 at 8:40
Unfortunately this didn't seem to work either. I still think it's Sprint
horking up the works due to the way they grab DNS requests and forward them on
your behalf. Thanks Sprint.
As a side note about the beta, I noticed there's a duplicate entry under
settings, "Enable WiFi-Encryption" shows up twice. When starting or stopping
tethering, it gives the message "Your phone is currently in an unknown state -
try to reboot!" (rebooting doesn't help). When starting tethering, the icon
duplicates itself, one above the other in addtion to the reboot message. Going
to home screen and back seems to eliminate the second icon, and tethering seems
to work ok. When stopping, the icon duplicates, gives the reboot message, then
goes back to one icon and seems to stop ok.
Original comment by jctrump
on 18 Apr 2011 at 5:57
> When starting tethering, the icon duplicates itself
Oh yeah. I was able to reproduce that. It happens if there is a delay when the
app requests "superuser"-permissions. If you have checked "always" and "ok" on
both start- and stop-requests that "problem" is gone on the next request(will
try to fix it tonight).
The dns-problem is weird.
What happens if you type:
nslookup google.com 8.8.8.8
in a console after you have connected? You could also try different nameserver
(instead of 8.8.8.8 which is a google-dns).
Original comment by harald....@gmail.com
on 18 Apr 2011 at 6:52
> "Enable WiFi-Encryption" shows up twice
Oh, yeah. Had that entry twice in a xml-file - no idea how I did manage that.
Fixed it already.
Original comment by harald....@gmail.com
on 18 Apr 2011 at 7:12
Mentioned issues should all be fixed in -pre14 - still not sure what's wrong
with your dns.
The version also includes a new feature: It allows to "hide" the ssid if the
setup-mothod "softap" is selected.
Original comment by harald....@gmail.com
on 18 Apr 2011 at 8:55
Sorry, I wasn't very clear. I'm able to use wifi tethering ok and browse the
web just fine on the pc...i.e. Sprint's DNS servers are working fine. OpenDNS
allows you to filter content, via their DNS servers by the following:
1. Set your PC dns servers to OpenDSN servers
2. Use their updater software to keep your WAN ip up to date on their servers
3. When you hit a particular website, their DNS servers see your requesting ip
and filter content according to settings you set via their website.
Here's OpenDNS's setup instruction page: https://store.opendns.com/setup/
What I think is happening is that Sprint is grabbing the requests that a normal
DNS server would forward on unmolested, and taking it as their own and shooting
it out...so the request never makes it to OpenDNS servers, or if it does, it's
coming from a completely different ip address than what the updater software is
reporting to OpenDNS as your WAN ip. I saw somewhere that Sprint does this,
but verizon doesn't, so it might work fine on a Verizon Android phone.
Not a huge deal...used to use it with land-based router and it worked great,
just trying to nerd out and see if there was a way to get it to work, or at
least why it wasn't working.
Thanks!
Original comment by jctrump
on 19 Apr 2011 at 12:16
Sprint @#$%ers.
http://forums.opendns.com/comments.php?DiscussionID=640
Original comment by jctrump
on 19 Apr 2011 at 6:27
Original issue reported on code.google.com by
jctrump
on 17 Apr 2011 at 8:31