Bug 7325 - Default gateway problems when using dialup & LAN together
Summary: Default gateway problems when using dialup & LAN together
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts   
(Show other bugs)
Version: 6.1
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-11-25 12:00 UTC by Rob Soulier
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-11-30 15:45:45 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Rob Soulier 1999-11-25 12:00:40 UTC
In my case I have configered my laptop for a LAN with a router (which is my
default gateway) for when I'm at my office, and a dialup PPP connection via
/dev/ttyS0 and my ISDN adapter to my ISP for when I'm elswhere e.g. at
home. When no LAN was configured PPP was fine. Since my LAN was configured
(with a default gateway) PPP gave me a connection that wouldn't work.
Debug told me PPP could not change the default gateway (although this
option was used). I found that this is solved by placing the call to pppd
in a wrapper script that does a 'route del -net 0.0.0.0 gw router-ip'
before calling pppd, and a 'route add default gw router-ip' after
disconnecting and stopping pppd. With de default gateway on eth0 out of the
way, pppd is able to establish the PPP peer as default gateway.
I don't know if this is a bug or a feature (or a user error), but this
behaviour (if a feature) might be doumented e.g. in the ppp-faq.
There is already another problem report on default gateways & ppp, with
another cause.

Regards,

Rob

Comment 1 Michael K. Johnson 1999-11-30 15:45:59 UTC
Please update to the latest initscripts.


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