Bug 602140 - Configuration reset every reboot
Summary: Configuration reset every reboot
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-09 08:50 UTC by Felipe Contreras
Modified: 2011-06-27 17:51 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2011-06-27 17:51:30 UTC

Attachments (Terms of Use)

Description Felipe Contreras 2010-06-09 08:50:08 UTC
Description of problem:
Each time I reboot, some fields the configuration for 'usb0' interface get reset, in particular, the MAC address.

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

How reproducible:

Steps to Reproduce:
1. Add usb0 interface
2. Remove MAC address
3. Save
4. Reboot
Actual results:
MAC address is reset

Expected results:
MAC address is cleared

Additional info:
This is useful because the usb0 MAC address is constantly changing.

Comment 1 Dan Williams 2010-06-15 18:27:01 UTC
Where are you doing the configuration and modification?  What program and/or file?

Comment 2 Felipe Contreras 2010-06-15 19:16:02 UTC
From the applet (nm-applet).

Comment 3 Dan Williams 2010-06-28 21:08:04 UTC
The MAC address in that field is actually for locking the connection you're editing to a specific piece of hardware.  Which won't work here since your hardware keeps changing MAC addresses.  You're looking for MAC spoofing which just got added to git master upstream, but won't be in NM 0.8.1 yet.

What hardware is this?

Comment 4 Felipe Contreras 2010-08-05 11:12:08 UTC
This is a Nokia N900.

But isn't it so that all usbnet devices have the same issues?

Anyway, I found out that depending on the order of how I create the configuration I get different behavior.

For example, it's different if I first connect the device and then configure usb0, or configure usb0 from scratch.

Comment 5 Bug Zapper 2011-06-02 11:29:17 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 6 Bug Zapper 2011-06-27 17:51:30 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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