Feature request: Ability to change more settings

[GoogleCodeExporter]

I was going to make this specific to setting the DNS server, but it can
probably be more generally defined as allow the user to change stuff in the
settings. I'll have to look into the source code and such and see if we
can't do this :)

Awesome job with the tethering app.

Original issue reported on code.google.com by dkowis on 4 Mar 2009 at 3:57

[GoogleCodeExporter]

Please make this less generic and file different issues for different types of
settings. We don't know what "more settings" means, specifically, and not all 
of them
will be of equal importance or difficulty. Sorry to be picky, but I hate to 
have to
guess at what you might mean or track 50 features in one Issue report.

Original comment by ulf...@gmail.com on 4 Mar 2009 at 4:29

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Sure.

I'd like to be able to change the DNS Server settings.

Also, change the Subnet one is using for DHCP. Like instead of 192.168.2.0, 
lets have
anything! :) I guess you could put in restrictions to require 192.168.* or 10.* 
or
172.16.144.* (if i remember my private subnets correctly...)

Being able to change the SSID has already been mentioned. 

I think these are the only two other configurable items in the setup (assuming 
we're
operating simply off the iptables based setup I read about all day today in the
forums :) )

Original comment by dkowis on 4 Mar 2009 at 4:33

[GoogleCodeExporter]

Thanks for the details. DNS and subnet should be close enough to merit only one
issue. They won't make it into .91, but maybe the next release.

Original comment by ulf...@gmail.com on 4 Mar 2009 at 5:20

[GoogleCodeExporter]

fwiw dns can be changed manually by pulling dnsmasq.conf, editing and pushing 
it back

however this is wrong, it should use dns servers provided by 3G connection, not 
static ones (or at least have option to choose from static or 3g-derived)

Original comment by notavail...@gmail.com on 11 Mar 2009 at 11:11

[GoogleCodeExporter]

Ah ... you're right. I've overlooked that.
Done some research. Problem will be that /etc/resolv.conf exists on JF's 
firmware but
NOT on stock adp-image. We could start dnsmasq with the flag
"resolv-file=/etc/ppp/resolv.conf" but we have to figure out before where the
resolv.conf-file is located on adp or how to create it.

A workaround would be to use MobileDataStateTracker and create the 
resolv.conf-file
out of the app. (a very ugly hack)

I will check that.

Original comment by harald....@gmail.com on 11 Mar 2009 at 1:48

• Changed state: Accepted

[GoogleCodeExporter]

ok ... MobileDataStateTracker does not exist in sdk1.0 anymore - so, that's a 
no go.

we have to use the "getprop" on shell.

# getprop net.dns1
and
# getprop net.dns2

will give the correct dns-servers of the 3g-connection. so, we have to update 
our
scripts for that.

Original comment by harald....@gmail.com on 11 Mar 2009 at 5:25

[GoogleCodeExporter]

DNS-Issue is fixed now:
http://code.google.com/p/android-wifi-tether/source/detail?r=42

Original comment by harald....@gmail.com on 11 Mar 2009 at 8:46

• Changed state: Fixed

[GoogleCodeExporter]

Great! Thanks.

(FWIW 4.2.2.2 is better than opendns, as at least it does not lie like opendns 
does.)

Original comment by notavail...@gmail.com on 13 Mar 2009 at 7:09