2009年11月28日 星期六

WIFI DNS ANDROID

android-porting
Thread Date
[android-porting] Re: android DNS fail to resolve website IP adddres
vinay
Tue, 03 Feb 2009 19:36:50 -0800

On Thu, Jan 29, 2009 at 11:47 AM, vinay wrote:

> hi,
>
> DNS started working after setting net dns proprty.. ,
> setprop net.dns1
>
> thanks,
> -vinay
>
> On Wed, Jan 21, 2009 at 12:10 PM, Sean McNeil wrote:
>
>>
>> eth1 isn't a valid device for tracking. Take a look at
>> frameworks/base/core/java/android/net/MobileDataStateTracker.java.
>> You'll see that it really only looks at rmnet0, eth0, and gprs. For DNS
>> to work, the net.dns# properties need to get set. You'll either have to
>> add eth1 into the MobileDataStateTracker, get the wifi to set net.dns#,
>> or change your kernel so the wifi is eth0.
>>
>> vinay wrote:
>> > hi,
>> > I have configured wifi with custom driver and able to connect to
>> > secured Access point. But IP resolv for website link is not
>> > happening. If I type IP address in the url then browser opens the
>> > site.
>> >
>> > Are there any known problems/limitations with DNS deployment in
>> > android on real target ?
>> >
>> > below getprop detaiils:--------------
>> > [dhcp.eth1.dns1]: [192.168.200.100]
>> > [dhcp.eth1.dns2]: []
>> > [dhcp.eth1.dns3]: []
>> > [dhcp.eth1.dns4]: []
>> > [dhcp.eth1.reason]: [BOUND]
>> > [dhcp.eth1.ipaddress]: [192.168.200.104]
>> > [dhcp.eth1.gateway]: [192.168.200.100]
>> > [dhcp.eth1.mask]: [255.255.255.0]
>> > [dhcp.eth1.leasetime]: [86400]
>> > [dhcp.eth1.server]: [192.168.200.100]
>> > [dhcp.eth1.result]: [ok]
>> >
>> > In browser AndroidManifest.xml ---------
>> > is
>> > also present.
>> >
>> > logcat detail below---------------
>> > I/ActivityManager( 1553): Starting activity: Intent
>> > { action=android.intent.ac
>> > tion.VIEW categories={android.intent.category.BROWSABLE} data=http://
>> > 164.129.225
>> > .192/ comp={com.android.browser/com.android.browser.BrowserActivity} }
>> > D/dalvikvm( 1672): GC freed 2989 objects / 215368 bytes in 144ms
>> > D/browser ( 1672): updating cursor
>> > D/dalvikvm( 1672): GC freed 4780 objects / 439912 bytes in 112ms
>> > W/KeyCharacterMap( 1672): No keyboard for id 0
>> > W/KeyCharacterMap( 1672): Using default keymap: /system/usr/keychars/
>> > qwerty.kcm.
>> > bin
>> > D/browser ( 1672): updating cursor
>> > I/ActivityManager( 1553): Starting activity: Intent
>> > { action=android.intent.acti
>> > on.VIEW categories={android.intent.category.BROWSABLE} data=http://
>> > stway.st.com/
>> > comp={com.android.browser/com.android.browser.BrowserActivity} }
>> > E/browser ( 1672): onReceivedError code:-2 The URL could not be found.
>> > D/browser ( 1672): updating cursor
>> >
>> > # cat /proc/net/route ------------
>> > Iface Destination Gateway Flags RefCnt Use
>> > Metric Mask M
>> > TU Window IRTT
>> > eth1 00C8A8C0 00000000 0001 0 0
>> > 0 00FFFFF0
>> >
>> > eth1 00000000 64C8A8C0 0003 0 0
>> > 0 00000000
>> >
>> > >
>> >
>>
>>
>> >>
>>
>

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

[android-porting] android DNS fail to resolve website IP adddres vinay
[android-porting] Re: android DNS fail to resolve website IP adddres Sean McNeil
[android-porting] Re: android DNS fail to resolve website IP adddres vinay
[android-porting] Re: android DNS fail to resolve website IP adddres vinay
Reply via email to

沒有留言:

張貼留言