Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 55264 - no chance to not modify default route in ifup-ippp
no chance to not modify default route in ifup-ippp
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-10-28 13:29 EST by Georg Baumann
Modified: 2014-03-16 22:24 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-29 15:18:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Georg Baumann 2001-10-28 13:29:31 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.7-10 i686)

Description of problem:
my ippp0 device connects to our office network; however
I have a DSL connection which I want to use as default
gateway. when using the ifup-ippp for starting and stopping
the ISDN connection, then the default route is always
modified because of:

>     options="$options defaultroute"

my solution, I have changed this to:
<     if [ "$DIALMODE" = "auto" ]; then
<       options="$options -defaultroute"
<     else
<       options="$options defaultroute"
<     fi

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

How reproducible:

Steps to Reproduce:
1.have a look into /etc/sysconfig/network-scripts/ifup-ippp

Additional info:
Comment 1 Bill Nottingham 2002-01-25 00:10:55 EST
Than, does this make sense? My concern is that this wouldn't do the right thing
for non-dial-on-demand situations where you still want the default route set.
Comment 2 Bill Nottingham 2005-09-29 15:18:01 EDT
Closing bugs on older, no longer supported, releases. Apologies for any lack of

If this persists on a current release, such as Fedora Core 4, please open a new bug.

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