Bug 72877 - Default gw is not updated when dialing ISDN
Summary: Default gw is not updated when dialing ISDN
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
(Show other bugs)
Version: 8.0
Hardware: i386 Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2002-08-28 17:17 UTC by Inger Karin Haarbye
Modified: 2014-03-17 02:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-29 20:16:26 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Inger Karin Haarbye 2002-08-28 17:17:23 UTC
Description of Problem: 
I usually have my default gateway via eth0( If I use "neat" to configure and dial 
ISDN-connection, the default gw is changed. That is OK, but when deactivating the ISDN 
connection, default gateway is not back to eth0 ( 
Version-Release number of selected component (if applicable): 
How Reproducible: 
tried 3 times. 
Steps to Reproduce: 
1.  configure isdn connection with neat 
2.  activating the new connection - gw is now set to ippp0/extern IP 
3.  deactivating ippp0 
Actual Results: 
Now I don't have a default gw at all. 
Expected Results: 
Default gw back to 
Additional Information:

Comment 1 Trond Eivind Glomsrxd 2002-08-28 18:11:03 UTC
Issues like this is handled by initscripts, not rhcn.

Comment 2 Inger Karin Haarbye 2002-10-06 09:39:57 UTC
The problem is still here in Psyche (RedHat 8.0). I usually use a default gw 
on my local network (ADSL). If I want to use my ISDN-connection with neat, the 
default gw is not restored when I deactivate ISDN-connection. I have to add my 
default route manually - or restart network.

Comment 3 Bill Nottingham 2005-09-29 20:16:26 UTC
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.