OK I can get this to happen if I need to, but it is really hard and normally happens when the pressure is on and time is of the essence. Now we don't use network manager and don't know if this works any better under that setup, but I doubt it. It certainly doesn't work well in our environment. We use the /etc/init.d/network setup. With the system administration network system to modify settings and static ips. Anyway once the system is generated the ethx and ethx:y devices are tied to specific card ids. This was brought into the structure a few versions ago. In general I actually very much approve of this. In the past I had adapters which switched device names and this caused unexpected system issues, and drove me crazy finding them. BUT cards do fail. If a card fails and you replace it you have to jump through more hoops than a dog in the circus to get the new card assigned to an existing device name. This is not good. How about some kind of a simple way to change this to the new value. You would think that going to system administration netywork and then select the device going to hardware and bind to MAC address would allow you to change this. But not quite. If the card still functions and what has happened is that the transciver has been blown this actually will work. The new card will come up as an additional device, and then you can switch the two mac addresses. Then you can power down and pull the offending card and repower up and delete the excess device. But if the new card has failed to the point that it is not functioning on the computer side of things this will not work. You can't move away from an existing MAC address unless it is still functional and the system can find it. Some kind of a utility for "this card is dead remove all references to it" needs to be implemented.
Thank you for the report. I'm switching component to system-config-network.
Let me know if screen shots are needed.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Still a problem under 13.
Still a problem under 14. Just had it happen in the last storm.
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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Interesting. Should this have not changed statuses when I switched it to 14?
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping