Bug 5365 - linuxconf hook in ifup-routes doesn't support all options
Summary: linuxconf hook in ifup-routes doesn't support all options
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: linuxconf
Version: 6.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-09-25 19:17 UTC by Donald Greer
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2000-02-10 19:30:01 UTC

Attachments (Terms of Use)

Description Donald Greer 1999-09-25 19:17:49 UTC
I am configuring a system that will have a default route
to the local lan, static routes to all local networks, but
will also have a dialup account as a backup.
  To make this work, I need to have a default route on eth0
with one metric (5) and one on ppp0 with another metric (2)
so that when the ppp0 comes up, packets to non-local
networks go that direction.
  I can add local networks in /etc/sysconfig/static-routes
and that works fine.but to get a metric on multiple default
routes, I have to add those default routes to the
static-routes table.  Apparently, if linuxconf is present
(and the appropriate ncurses library) you use "linuxconf
--hint route "$1"" (where $1 is the interface).  Linuxconf
ignores the "metric X" statement, so I can't set metrics.
  I can add the routes as "eth0 net netmask
metric 5" but it doesn't make a difference.
  I've worked around it by hacking ifup-routes to disregard
linuxconf, but that's certainly not the optimal solution.
  Please add "metric" support to linuxconf if possible (or
add it to the wish list for the development team).  Also,
please allow me to override linuxconf for routing (say with
a line in static-routes "linuxconf no" that gets checked
before checking for linuxconf).

Comment 1 Michael K. Johnson 1999-11-18 23:57:59 UTC
Added Jacques to the CC line to prime a discussion about adding metrics...

Comment 2 Brent Fox 2002-06-05 04:12:11 UTC
Closing since we don't ship linuxconf anymore.

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