Bug 375481 - NetworkManager should not assume all links are DHCP enabled
NetworkManager should not assume all links are DHCP enabled
Status: CLOSED DUPLICATE of bug 134886
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-11-11 00:13 EST by Tim Taiwanese Liim
Modified: 2007-11-30 17:12 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-13 12:02:42 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim Taiwanese Liim 2007-11-11 00:13:28 EST
Description of problem:
    NetworkManager starts DHCP client for all types of interfaces,
    even for those with static IP address.  This is very bad for
    servers, where static IP is much desired, and NetworkManager
    really helps to maintain network connectivity.

    Related to bug374861, issue #1
       1.  Network Manager will not connect using STATIC ip addressing.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. ifconfig eth0 down
2. NetworkManager --no-daemon
3. ifconfig eth0 up
Actual results:
    NetworkManager starts dhclient and changes eth0 IP.

Expected results:
    eth0 should keep the static IP address as assigned
    by "ifconfig eth0 up".

Additional info:
    work around for servers that requires static IP:
    disable NetworkManager, by using system-config-services.
Comment 1 Dan Williams 2007-11-13 12:02:42 EST

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

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