Bug 458822 - Network Manager does not save custom DNS settings
Summary: Network Manager does not save custom DNS settings
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 9
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-12 14:28 UTC by markm
Modified: 2008-11-02 22:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-11-02 22:20:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description markm 2008-08-12 14:28:16 UTC
Description of problem:

Network manager does not save custom DNS settings - just drops them without any warning.

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

NetworkManager Applet 0.7.0
NetworkManager-0.7.0-0.11.svn3846.fc9@i386

How reproducible:

always

Steps to Reproduce:
1. open an existing wireless connection / create a new connection
2. on the IPv4 Settings page do:
 * Method: Manual or Automatic with manual DNS settings
 * Addresses: Address: 192.168.0.23 Prefix: 24 Gateway: 192.168.0.1
 * DNS Servers: 208.67.222.222, 208.67.220.220
3. Press 'OK' button
4. Select your connection and click “edit” button on the side
  
Actual results:

everything is set as request but DNS Servers, field remains empty

Expected results:

Network Manager remembers manual DNS settings

Additional info:

It used to work, I've set up another connection couple of months ago and it remembered manual DNS Settings, this time it does not work, even after a computer restart. It is a really bad user experience - I just flew in to Spain and wanted to use internet, Network Manager does not allow me to do so - I had to write a simple cron job which overwrites /etc/resolv.conf every couple of minutes with correct DNS settings.

Comment 1 Dan Williams 2008-11-02 22:20:52 UTC
Should be fixed in latest updates (svn4022 and later).


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