network-manager does not take into account static configurations *properly*
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Confirmed
|
High
|
Tollef Fog Heen |
Bug Description
Binary package hint: network-manager
taken from http://
I have a static IP set using gnome's network-admin tool, but network-manager is installed (some metapackage depends on it).
All the applications that are networkmanager-
I would mark this bug as *major* because it is a regression for those who have static IP setups and will see their apps break when they dist-upgrade their ubuntu boxes. Their webpages will refuse loading, and they will have no idea why, as their network seems to "behave normally" (for all networkmanager-
Reply from upstream: "This is actually expected behavior. NM is not supposed to respect the setup of distro-specific tools."
description: | updated |
Changed in network-manager: | |
importance: | Undecided → High |
status: | Unconfirmed → Confirmed |
Changed in network-manager: | |
assignee: | nobody → tfheen |
assignee: | tfheen → pitti |
Changed in network-manager: | |
assignee: | pitti → tfheen |
------- Comment #3 from Dan Williams 2007-02-26 12:32 UTC ------- interfaces. Therefore, to NM that interface doesn't exist, and you'll get the behavior your see.
NM actually has some support for static IP settings already, but the distro specific backend has to support it. Fedora, SUSE, and Debian support it. But Ubuntu decided to make NM ignore _any_ interface that you have already configured in /etc/network/