vexpress: ECM does not set DNS address

Bug #915434 reported by Tixy (Jon Medhurst) on 2012-01-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Android
Fix Released
Kejun ZHOU
Fix Released

Bug Description

Bug #894502 added the Ethernet Configuration Manager to ICS however, on vexpress at least, this doesn't set the DNS address after it performs a DHCP lookup.

The attached logcat output shows that DHCP gets a DNS address (see line with "DHCP request succeeded").
However "getprop net.dns1" gives a blank like, and domain names can't be resolved with ping, or in the Browser.

Tixy (Jon Medhurst) (tixy) wrote :
Zach Pfeffer (pfefferz) on 2012-01-12
Changed in linaro-android:
assignee: nobody → Kejun ZHOU (kejun-zhou)
importance: Undecided → High
milestone: none → 12.01
Kejun ZHOU (kejun-zhou) on 2012-01-16
Changed in linaro-android:
status: New → In Progress
Kejun ZHOU (kejun-zhou) wrote :
Changed in linaro-android:
status: In Progress → Fix Committed
Changed in linaro-landing-team-arm:
importance: Undecided → High
status: New → Won't Fix

It works on my side with build landing-snowball 133, let's see what happens when Abhishek tests it.

Observation on build :
After bootup with ethernet cable connected following are the observations:

1. Ethernet interface is DOWN(cheked via netcfg command) and device do not get IP - randomly observed (~1/10 times)

2. Ethernet interface is UP (cheked via netcfg command) but device gets IP in different range than expected ,
Expected is 192.168.1.xx but device gets ip 192.168.0.xx - Now browsing does not work
Tried to reassign the ip via command - "netcfg eth0 dhcp" - now device gets ip in range 192.168.1.xx - Still browsing does not work
Now manually setting for dns is done via " setprop net.dns1" - Now browsing works.(can open

Behavior 2 is pretty consistent on my setup . Ethernet settings in settings menu are not changed(defalt via dhcp)

So the issue - "Unable to browse after bootup with ethernet cable connected" still remains valid. If this is the correct bug-id to track this issue I suggest to keep this issue open.

Changed in linaro-landing-team-arm:
milestone: none → 2012.01
status: Won't Fix → Fix Committed
Changed in linaro-landing-team-arm:
status: Fix Committed → Fix Released
Changed in linaro-android:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments