Bug 124045 - Support setting a metric on interface routes
Support setting a metric on interface routes
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: initscripts (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
: FutureFeature
: 131056 (view as bug list)
Depends On:
Blocks: FC5Target
  Show dependency treegraph
 
Reported: 2004-05-23 01:37 EDT by Nickolai Zeldovich
Modified: 2014-03-16 22:45 EDT (History)
3 users (show)

See Also:
Fixed In Version: 8.34-1
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-05-23 15:21:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Patch for /sbin/ifup (1.86 KB, patch)
2004-05-23 01:37 EDT, Nickolai Zeldovich
no flags Details | Diff

  None (edit)
Description Nickolai Zeldovich 2004-05-23 01:37:15 EDT
The attached patches allow the user to specify a metric for the routes
of a given interface.  For instance, if they have two interfaces and
prefer one over another, whenever both are up, they can set the metric
values of the two interfaces appropriately and use the preferred one
when both are available.

This particular patch is for /sbin/ifup only -- i.e. just for
statically configured interfaces.  I'll clean up my patch for
/sbin/dhclient-script shortly -- in the meantime, do you think it'd be
best for me to open a second bug report for the dhclient-script
change?  They're really the same change, but for some reason Redhat
decided to split the logic across two packages.

-- kolya
Comment 1 Nickolai Zeldovich 2004-05-23 01:37:43 EDT
Created attachment 100470 [details]
Patch for /sbin/ifup
Comment 2 Bill Nottingham 2005-09-30 17:35:39 EDT
*** Bug 131056 has been marked as a duplicate of this bug. ***
Comment 3 Bill Nottingham 2006-05-23 15:21:40 EDT
A fix for this is in 8.34-1.

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