Bug 230699 - ifdown effectively brings downs all interfaces by removing routes instead of replacing them
Summary: ifdown effectively brings downs all interfaces by removing routes instead of ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts
Version: 5
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard: bzcl34nup
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-03-02 11:00 UTC by Fred van Nijnatten
Modified: 2014-03-17 03:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-05-06 19:18:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Fred van Nijnatten 2007-03-02 11:00:50 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.10) Gecko/20070216 Firefox/1.5.0.10

Description of problem:
I have 2 ethernet interfaces (both using DHCP). When I run ifup on an interface the default route and the zeroconf route are replaced to make use of that interface. But when I run ifdown on that interface the routes are removed, practically disabling both interfaces. I would expect ifdown to change the routes back to another active interface.

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


How reproducible:
Always


Steps to Reproduce:
1. /sbin/ifup eth0
2. /sbin/ifup eth1
/sbin/route shows
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
172.16.12.0     *               255.255.255.0   U     0      0        0 eth0
172.16.12.0     *               255.255.255.0   U     0      0        0 eth1
169.254.0.0     *               255.255.0.0     U     0      0        0 eth1
default         172.16.12.1     0.0.0.0         UG    0      0        0 eth1

3. /sbin/ifdown eth1
/sbin/route shows
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
172.16.12.0     *               255.255.255.0   U     0      0        0 eth0

Actual Results:
the default route to the gateway is removed.

Expected Results:
The default route to the gateway is replaced to make use of the other card.

Additional info:

Comment 1 Bug Zapper 2008-04-04 06:25:34 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
http://fedoraproject.org/wiki/LifeCycle/EOL

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 2 Bug Zapper 2008-05-06 19:18:05 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus 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.