Bug 399204 - Networkmanager drops DHCP configuration
Summary: Networkmanager drops DHCP configuration
Status: RESOLVED DUPLICATE of bug 402575
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: GNOME (show other bugs)
Version: RC 3
Hardware: All openSUSE 11.0
: P3 - Medium : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-11 09:43 UTC by Lars Müller
Modified: 2008-08-25 09:36 UTC (History)
1 user (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Networkmanager log (34.21 KB, text/plain)
2008-06-11 09:48 UTC, Lars Müller
Details
Excerpt of /var/log/messages while dhclient is under NM control (1.85 KB, text/plain)
2008-06-11 09:54 UTC, Lars Müller
Details
strace of NetworkManager (15.89 KB, text/plain)
2008-06-17 10:17 UTC, Lars Müller
Details
diff of the non and the working dhclient.conf (944 bytes, text/plain)
2008-06-17 11:46 UTC, Lars Müller
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Müller 2008-06-11 09:43:16 UTC
After a short amount of time networkmanager drops the IP configuration.

Calling dhclient from the command line with the interface as argument works as expected.
Comment 1 Lars Müller 2008-06-11 09:48:10 UTC
Created attachment 221452 [details]
Networkmanager log
Comment 2 Lars Müller 2008-06-11 09:54:31 UTC
Created attachment 221455 [details]
Excerpt of /var/log/messages while dhclient is under NM control
Comment 3 Lars Müller 2008-06-11 09:56:49 UTC
The time frame in question is Jun 11 11:33:04 to 11:33:49.
Comment 4 Lars Müller 2008-06-11 10:02:40 UTC
LC_ALL=POSIX rpm -qa --last | grep ^NetworkManager
NetworkManager-kde-0.7r815970-4.1             Tue Jun 10 16:01:30 2008
NetworkManager-0.7.0.r3685-7.1                Tue Jun 10 15:55:38 2008
NetworkManager-glib-0.7.0.r3685-7.1           Tue Jun 10 15:46:08 2008
Comment 5 Tambet Ingo 2008-06-11 10:08:14 UTC
This looks like a dbus issue. NM uses it's own script that runs when dhclient succeeds. It's purpose is to convert the environment variables from dhclient to dbus message and send it to NM. This usually fails because the script can not obtain dbus connection and that happens when dbus configuration files in /etc/dbus-1/ change. For some reason, dbus is not able to work correctly after that until it's restarted or receives a SIGHUP signal. Can you confirm the problem dissapears after reboot?
Comment 6 Lars Müller 2008-06-11 11:12:29 UTC
I've rebooted the systenm several times and the problem is still there.

dbus is activated and running.

These are the dbus packages in use:

dbus-1-qt3-0.62-179.1
libdbus-1-qt3-0-0.8.1-24.1
dbus-1-glib-0.74-88.1
dbus-1-1.2.1-15.1
dbus-1-x11-1.2.1-18.1
dbus-1-devel-1.2.1-15.1
Comment 7 Tambet Ingo 2008-06-11 11:39:20 UTC
NM runs dhclient like this:

/sbin/dhclient -d -sf /usr/lib/NetworkManager/nm-dhcp-client.action -cf /etc/dhclient.conf eth0

Could you please try to kill NetworkManager, then 'ifconfig eth0 up' and the dhclient command line from above. Does that work? In case of dbus errors I suspect, it should print out something like:

Error: Could not acquire the NM DHCP client service. Message: (org.freedesktop.DBus.Error.AccessDenied) Connection ":1.1598" is not allowed to own the service "org.freedesktop.nm_dhcp_client" due to security policies in the configuration file
Comment 8 Lars Müller 2008-06-11 13:07:27 UTC
The dhclient command line from comment #7 works.
Comment 9 Lars Müller 2008-06-17 10:17:32 UTC
Created attachment 222436 [details]
strace of NetworkManager

This is a strace of NetworkManager started with an unplugged cable.  Later the cable gets plugged.
Comment 10 Lars Müller 2008-06-17 11:45:23 UTC
/etc/dhclient.conf was installed as /etc/dhclient.conf.rpmnew.

I suspec this line

    script "/sbin/dhclient-script";

to cause the trouble.
Comment 11 Lars Müller 2008-06-17 11:46:10 UTC
Created attachment 222475 [details]
diff of the non and the working dhclient.conf
Comment 12 Hannes Reinecke 2008-08-14 11:36:44 UTC
Confirmed here. Why is this closed with INVALID? It certainly is a problem here, found during update from 10.3 to 11.0.
Comment 13 Lars Müller 2008-08-14 12:45:11 UTC
As it works with the default dhclient configuration.

Please check the diff of my old working configuration attached with comment #11 compared to your situation.  If the situation is the same we have a generic 10.3 to 11.0 upgrade problem anyone using networkmanager/ dhclient will run into.
Comment 14 Hannes Reinecke 2008-08-25 09:22:01 UTC
Situation is the same. The first hunk is not required, but the second one (which comments out the 'script' line still applies and fixes the problem.

Looks like a generic update problem.
Comment 15 Tambet Ingo 2008-08-25 09:36:09 UTC
Marking this one as duplicate because the other has more information.

*** This bug has been marked as a duplicate of bug 402575 ***