Batteries included
AEblefisk
Posts: 4
Joined: 26 Nov 2013, 23:44

DNS problems with Nexus 7 (2012) running Android 4.4

Post by AEblefisk » 27 Nov 2013, 00:22

I just upgraded to 4.4 and the good news is that my Huawei E1752 can connect to the internet.
The problem/challenge/interesting part is that name resolution isn't working. I can ping 195.249.80.32 OK but if I try to ping google.com it answers unknown host.
Any ideas/suggestions? What can I do to fix it?
Last edited by AEblefisk on 07 Dec 2013, 23:11, edited 1 time in total.

cominox
Posts: 1
Joined: 28 Nov 2013, 13:25

Re: Positive news for Nexus 7 (2012) running Android 4.4

Post by cominox » 28 Nov 2013, 13:27

Excuse me , can you please tell me what kernel you are using ?

AEblefisk
Posts: 4
Joined: 26 Nov 2013, 23:44

Re: Positive news for Nexus 7 (2012) running Android 4.4

Post by AEblefisk » 28 Nov 2013, 20:51

It says 3.1.10-gee1a0b2

dtg7
Posts: 34
Joined: 04 Aug 2013, 11:12

Re: Positive news for Nexus 7 (2012) running Android 4.4

Post by dtg7 » 28 Nov 2013, 23:48

a.k.a. stock kernel. is there a custom kernel out for 4.4?

Googling OP's issue I found someone discussing a similar issue (but non-android) where they say they could access the google website using the ip address http://74.125.224.72/ but not google.com. So I tried that in the chrome browser and sure enough it goes to the google site and you can make a search but you can't follow the search result links. so yes this seems to indicate a dns problem. But I think the bigger problem is the system not being network aware, and maybe not being network aware is causing dns issues.

So I think this issue can only be solved by another update from Josh.
Might be better to hold off updating to 4.4 till then.

tux
Posts: 4
Joined: 29 Nov 2013, 00:49

Re: Positive news for Nexus 7 (2012) running Android 4.4

Post by tux » 29 Nov 2013, 01:02

I'm seeing a similar issue with Asus Nexus 7 16Gb 2012 / Android 4.4 KRT16S and modem ZTE MF190: it's connecting, but DNS resolution is not working.
Here is the log captured from PPP Widget:
PPP Widget version 1.3.3
USB_ModeSwitch log from Thu Nov 28 21:36:03 EET 2013

Raw args from udev: 2-1/2-1:1.0

Using top device dir /sys/bus/usb/devices/2-1
----------------
USB values from sysfs:
manufacturer ZTE,Incorporated
product ZTE WCDMA Technologies MSM
serial MF1900RDSD010000
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/19d2.2000
! matched. Reading config data
devList 1:
config: TargetVendor set to 19d2
config: TargetProductList set to 0001,0002,0015,0016,0017,0031,0037,0052,0055,0061,0063,0064,0066,0091,0108,0117,0128,0157,0177,1402,2002,2003
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1

Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 2 -g 4 -v 19d2 -p 2000 -f $cB

Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------

Reading long config from command line

* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.7 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)

! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor= 0x19d2
DefaultProduct= 0x2000
TargetVendor= 0x19d2
TargetProduct= not set
TargetClass= not set
TargetProductList="0001,0002,0015,0016,0017,0031,0037,0052,0055,0061,0063,0064,0066,0091,0108,0117,0128,0157,0177,1402,2002,2003"

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
QuantaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
BlackberryMode=0
PantechMode=0
MessageEndpoint= not set
MessageContent="5553424312345678000000000000061e000000000000000000000000000000"
MessageContent2="5553424312345679000000000000061b000000020000000000000000000000"
MessageContent3="55534243123456702000000080000c85010101180101010101000000000000"
NeedResponse=1
ResponseEndpoint= not set

InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled

Use given bus/device number: 002/004 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 19d2:2000
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)

USB description data (for identification)
-------------------------
Manufacturer: ZTE,Incorporated
Product: ZTE WCDMA Technologies MSM
Serial No.: MF1900RDSD010000
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Reading the response to message 1 (CSW) ...
OK, response successfully read (13 bytes).
Trying to send message 2 to endpoint 0x01 ...
OK, message successfully sent
Reading the response to message 2 (CSW) ...
OK, response successfully read (13 bytes).
Trying to send message 3 to endpoint 0x01 ...
OK, message successfully sent
Reading the response to message 3 (CSW) ...
Response reading got error -32
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.

ok:busdev
--------------------------------
(end of usb_modeswitch output)

Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 19d2:0117 (ZTE,Incorporated: ZTE WCDMA Technologies MSM)
Device class of first interface is ff
Now checking for bound driver ...
Driver has bound, device is known

All done, exiting

Using port ttyUSB2 for connection
ATE1
OK
AT+CFUN=1
OK
AT+CGDCONT=1,"IP","internet"
OK
ATD*99#
CONNECT
Report from chat:

chat: Nov 29 00:07:14 CONNECT 7200000
Serial connection established.
using channel 8
Using interface ppp0
Connect: ppp0 <--> /dev/ttyUSB2
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x59293631>]
rcvd [LCP ConfReq id=0x12 <asyncmap 0x0> <auth chap MD5> <magic 0x1a63043> <pcomp> <accomp>]
No auth is possible
sent [LCP ConfRej id=0x12 <auth chap MD5> <pcomp> <accomp>]
rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x59293631>]
rcvd [LCP ConfReq id=0x13 <asyncmap 0x0> <magic 0x1a63043>]
sent [LCP ConfAck id=0x13 <asyncmap 0x0> <magic 0x1a63043>]
sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
rcvd [LCP DiscReq id=0x14 magic=0x1a63043]
rcvd [IPCP ConfNak id=0x1 <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14> <ms-wins 10.11.12.13> <ms-wins 10.11.12.14>]
sent [IPCP ConfReq id=0x2 <addr 0.0.0.0> <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14>]
rcvd [IPCP ConfNak id=0x2 <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14> <ms-wins 10.11.12.13> <ms-wins 10.11.12.14>]
sent [IPCP ConfReq id=0x3 <addr 0.0.0.0> <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14>]
rcvd [IPCP ConfNak id=0x3 <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14> <ms-wins 10.11.12.13> <ms-wins 10.11.12.14>]
sent [IPCP ConfReq id=0x4 <addr 0.0.0.0> <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14>]
rcvd [IPCP ConfReq id=0xc]
sent [IPCP ConfNak id=0xc <addr 0.0.0.0>]
rcvd [IPCP ConfNak id=0x4 <addr 172.22.251.71> <ms-dns1 193.231.252.1> <ms-dns3 213.154.124.1>]
sent [IPCP ConfReq id=0x5 <addr 172.22.251.71> <ms-dns1 193.231.252.1> <ms-dns3 213.154.124.1>]
rcvd [IPCP ConfReq id=0xd]
sent [IPCP ConfAck id=0xd]
rcvd [IPCP ConfAck id=0x5 <addr 172.22.251.71> <ms-dns1 193.231.252.1> <ms-dns3 213.154.124.1>]
Could not determine remote IP address: defaulting to 10.64.64.64
local IP address 172.22.251.71
remote IP address 10.64.64.64
primary DNS address 193.231.252.1
secondary DNS address 213.154.124.1
Script /data/data/de.draisberghof.pppwidget/app_bin/ip-up started (pid 7778)
Script /data/data/de.draisberghof.pppwidget/app_bin/ip-up finished (pid 7778), status = 0x0
Terminating on signal 15
Connect time 2.8 minutes.
Sent 65431 bytes, received 2527501 bytes.
Script /data/data/de.draisberghof.pppwidget/app_bin/ip-down started (pid 8201)
sent [LCP TermReq id=0x2 "User request"]
rcvd [LCP TermAck id=0x2]
Connection terminated.
Script /data/data/de.draisberghof.pppwidget/app_bin/ip-down finished (pid 8201), status = 0xff

Any idea how to fix ? Thank you!

dtg7
Posts: 34
Joined: 04 Aug 2013, 11:12

Re: Positive news for Nexus 7 (2012) running Android 4.4

Post by dtg7 » 29 Nov 2013, 15:40

Ok here is the positive news. While trying different apps I found one that works but luckily it was a browser namely Firefox Browser (probably the best browser for Android.) Looks like we at 4.4 can at least browse the web. Better than nothing till we get an update. If you use ppp widget with stuff like skype avoid kitkat for now.

nigel
Posts: 7
Joined: 04 Dec 2013, 04:34

Re: Positive news for Nexus 7 (2012) running Android 4.4

Post by nigel » 04 Dec 2013, 04:40

I fixed this.

The issue is Nexus on Android 4.4 with PPPWidget does NOT replace the DNS server names when connecting to your USB modem.

The workarounds:

Get your router, instead of giving itself as the DNS server, to give an Internet DNS server, like from your ISP or generic, e.g. 8.8.8.8 for Google's DNS server. Then when you connect to USB modem, the DNS resolving will still work.

Disable Wifi before you connect so you have NO DNS server, then it seems to default itself when NO DNS server to using Google's own anyway.

I also fixed Nexus 10 via a kernel patch.

dtg7
Posts: 34
Joined: 04 Aug 2013, 11:12

Re: Positive news for Nexus 7 (2012) running Android 4.4

Post by dtg7 » 04 Dec 2013, 22:27

Well, it's a step forward anyway. This trick expands the usable apps to any app that doesn't require network notification. From what I checked, this includes all browsers (so you're not stuck with Firefox), Twitter app, and Tango app. Unfortunately this still excludes some major apps like the Play Store, Skype, Viber, YouTube (here search works but can't watch), Maps, and so on. So most apps still require network notification and only an updated ppp widget would do that.

The trick is : go to settings->wifi connect to an available wifi network. then long press on that network and select modify network. now check the box for "show advanced options" when those show up click on the box next to ip settings and change it from dhcp to static. more settings show up. scroll down to the dns settings and change dns 1 to 8.8.8.8 Disconnect from the wifi network and ppp widget should now provide limited connectivity. if you connect to a different wifi network (one that you haven't changed to static dns) or if you restart your tablet you'll have to reconnect to the modified wifi network again before using ppp widget.

btw back when I was googling op's issue (up top) and noticed the dns issue, I also came across the possible use of google's public dns servers. I attempted to employ it from the terminal emulator but it didn't help and still doesn't work that way, at least for me.

niflheim
Posts: 4
Joined: 06 Dec 2013, 13:15

Re: Positive news for Nexus 7 (2012) running Android 4.4

Post by niflheim » 06 Dec 2013, 13:27

hy, i also have this issue.what I want to add is that nslookup google.com works ok.(this is weird because nslookup uses the current dns, but ping or http dns translation does not work)

niflheim
Posts: 4
Joined: 06 Dec 2013, 13:15

Re: Positive news for Nexus 7 (2012) running Android 4.4

Post by niflheim » 07 Dec 2013, 08:45

I would like to suggest to the creator of this thread that he should modify the title adding Dns problem to it so that it pops out with the problem we are experiencing.

AEblefisk
Posts: 4
Joined: 26 Nov 2013, 23:44

Re: DNS problems with Nexus 7 (2012) running Android 4.4

Post by AEblefisk » 07 Dec 2013, 23:13

Thanks everybody who contributed. With the workaround for DNS a lot of apps can now be used with PPPwidget.
niflheim wrote:I would like to suggest to the creator of this thread that he should modify the title adding Dns problem to it so that it pops out with the problem we are experiencing.
Good idea, I'll do that.

dtg7
Posts: 34
Joined: 04 Aug 2013, 11:12

Re: DNS problems with Nexus 7 (2012) running Android 4.4

Post by dtg7 » 09 Dec 2013, 11:11

* It should be noted that the issue in this thread is specific to PPP Widget 1.3.3 and any future version will probably fix network notification which should fix the dns problems and make everything here unnecessary.
----------------------------------------------

I didn't like the idea of being tied to a wifi based solution because it was basically a tethered solution. Every time you connect to a new wifi network or if you restart your tablet you have to go thru the workaround. But android 4.4 wouldn't let us change dns through the terminal. In fact, googling around, it seems that how dns is handled changed starting from 4.3 to an extent that all the dns changing apps in the play store (there are many) were rendered useless. Like I alluded to in my asterix note above, ppp widget seems to have avoided this issue by declaring itself as a wifi connection, which I think is why it works with 4.3, and hopefully 4.4 once updated.

So if terminal doesn't let us change dns on the fly, the only other solution would be to modify the system at startup. As I'm not myself able to do that, I had to google around. This led me to something called dnsproxy2 in one xda thread, at the end of which someone mentioned another thread for something called CrossBreeder, which makes use of dnsproxy2. Reading up on Crossbreeder it was clear that it would do exactly what I was looking for. It does other things too, but right now I was only interested in its dns handling. So I decided to give it a try and it works perfectly.

Things to note:
- CrossBreeder is in fact a system mod, meaning it will add/edit system files. Not exactly as much change as a custom kernel but still significant. So it is important to make a nandroid backup of your device in its working state before employing the mod. You can save the backup on your computer and use it in case something goes wrong. Know what you're doing as only you are responsible for your actions.
- Installing and uninstalling is done very easily by flashing the provided zip files in a custom recovery. I'm using the CrossBreeder_7.2.13 version because it has an accompanying uninstall zip, while the newest version doesn't have one yet (explicitly anyway). Read the xda main posts (first page), they explain everything.
- OTA updates: You'll have to uninstall the mod before you can install ota updates. They don't like system files messed with. Crossbreeder will restore all stock files when uninstalled.

http://forum.xda-developers.com/showthr ... ?t=2113150
Last edited by dtg7 on 11 Dec 2013, 10:42, edited 1 time in total.

niflheim
Posts: 4
Joined: 06 Dec 2013, 13:15

Re: DNS problems with Nexus 7 (2012) running Android 4.4

Post by niflheim » 10 Dec 2013, 11:43

android 4.4.2 for nexus is released today over ota
( http://www.androidpolice.com/2013/12/09 ... -updating/ ).
maybe this fixes our problem.

niflheim
Posts: 4
Joined: 06 Dec 2013, 13:15

Re: DNS problems with Nexus 7 (2012) running Android 4.4

Post by niflheim » 10 Dec 2013, 20:35

tried with 4.4.2, no change (I have ZTE MF-190 dongle)

dtg7
Posts: 34
Joined: 04 Aug 2013, 11:12

Re: DNS problems with Nexus 7 (2012) running Android 4.4

Post by dtg7 » 11 Dec 2013, 10:51

yeah same here. that's expected though since this is not a bug or error, it's a "feature" ie google intentionally changed dns handling starting from 4.3. But at least wifi networks seem to be exempt so ppp widget will hopefully be fine when Josh gets it going for 4.4 kernel. Limited connectivity with crossbreeder till then.

Post Reply