Bug 8039 - PPP config trouble.
PPP config trouble.
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Nalin Dahyabhai
Depends On:
  Show dependency treegraph
Reported: 1999-12-29 01:46 EST by jxdxbx
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-02-10 14:30:02 EST
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 jxdxbx 1999-12-29 01:46:30 EST
With Redhat 6.1 I've been unable to properly install PPP.  All
the guidebooks tell me to do it from linuxconfig, which I do.

I set up the connection as well as the DNS name.  All this I
do by the book.

But, PPP doesn't work unless I /also/ set it up with this other
configuration utility,  on the Internet menu of Gnome, called
Dial Up Manager or something.  Even if I set up a connection
with linuxconfig and it lists it, it will always give me the
"Set up new connection" dialog box.  I eventually find a way to
set everything up, doubling my work, and get PPP to work.  Then
I put in a secondary DNS address which later turns out to be
invalid, making PPP not work again.  I keep going into both
programs and attempting to get rid of this spurious information,
and I do.  But then I go back to check if it's gone, and lo, it's
still there.  I cannot alter the DNS addresses.

I am now downloading what claims to be an update of linuxconfig.
I am doing this through windows because it works and linux
doesn't.  I only hope it doesn't screw everyrthing up royally,
like when I tried installing wheel-mouse support, and midnight
commander wouldn't work anymore.
Comment 1 Trond Eivind Glomsrxd 2000-09-13 18:54:20 EDT
this should be fixed both in 6.2, and in pinstripe, where rp3 is the default
tool for setting up ppp.

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