Bug 10270 – DHCP does not seem to create /etc/resolv.conf

Bug 10270 - (int-171305) DHCP does not seem to create /etc/resolv.conf

(int-171305)
Summary:	DHCP does not seem to create /etc/resolv.conf

Status:	RESOLVED FIXED

Product:	Connectivity
Component:	Networking
Version:	5.0/(3.2010.02-8)
Platform:	All Maemo

Importance:	Unspecified normal (vote)
Target Milestone:	5.0/(10.2010.19-1)
Assigned To:	unassigned
QA Contact:	networking-bugs

URL:
Keywords:	patch

Depends on:
Blocks:
	Show dependency tree

Reported:	2010-05-25 19:07 UTC by M
Modified:	2010-05-28 18:30 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description M (reporter) 2010-05-25 19:07:00 UTC

SOFTWARE VERSION:
3.2010.02-8

EXACT STEPS LEADING TO PROBLEM: 
1. Connect to some network
2. Observe /etc/resolv.conf
3. Does not appear
4. Instead I've /var/run/resolv.conf.gprs or .wlan


EXPECTED OUTCOME:
resolv.conf should be symlinked to /var/run/


REPRODUCIBILITY:
Well, ok, while not observing this problem after a fresh install, it started
ocurring reproducably after installing several (essential) apps from maemo.org.

Patching /etc/maemo-dhcp.d/50_ipv4_network_setup so that a symlink is created
fixes the problem for wlan0 but not quite for gprs0:

--- new       2010-05-25 17:47:32.000000000 +0200
+++ original:/etc/maemo-dhcp.d/50_ipv4_network_setup 2009-11-03
14:41:05.000000000 +0100
@@ -55,8 +55,6 @@
              done

              mv $RESOLV_CONF.tmp $RESOLV_CONF
-              rm -f /etc/resolv.conf
-              ln -s $RESOLV_CONF /etc/resolv.conf

              # Clear dnsmasq cache after getting new nameservers
              kill -SIGHUP `pidof dnsmasq`



EXTRA SOFTWARE INSTALLED:
a lot of

OTHER COMMENTS:
Sorry for messing around


User-Agent:       Mozilla/5.0 (compatible; Konqueror/4.4; Linux) KHTML/4.4.3
(like Gecko)

Comment 1 M (reporter) 2010-05-28 18:29:15 UTC

Good news:

Upgrading to PR2 overwrote my patches and fixed the issue. So,
libicd-network-ipv4-0.25+0m5 fixes my issue.

M.

Comment 2 Andre Klapper maemo.org

2010-05-28 18:30:28 UTC

Ah, nice! Thanks for updating :)