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 8765 - after connection is made, rp3 still says "waiting to connect ..."
after connection is made, rp3 still says "waiting to connect ..."
Product: Red Hat Linux
Classification: Retired
Component: rp3 (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Depends On:
  Show dependency treegraph
Reported: 2000-01-23 06:50 EST by Chris Runge
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-04-06 16:39:21 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 Chris Runge 2000-01-23 06:50:49 EST
I use the RH PPP Dialer to connect to the Internet.  It displays "Waiting
to connect to Mindspring", then actually does connect, but the "Waiting to
connect to Mindspring" still stays up.

$ rpm -q rp3 wvdial initscripts
Comment 1 Jules Stuifbergen 2000-01-31 08:00:59 EST
I experienced the same problem, with newer rpms.


There's no option to disable PEERDNS. My resolv.conf gets overwritten when using
rp3, (not when debugging with rp3-config).
Comment 2 Nalin Dahyabhai 2000-03-06 10:20:59 EST
The key package as far as the "waiting to connect..." dialog is concerned is
initscripts.  Newer initscripts packages also preserve the contents of your
resolve.conf if the nameservers returned by pppd are already in there.  Peer DNS
can be toggled off by adding the line
to the appropriate file in /etc/sysconfig/network-scripts.
Comment 3 Nalin Dahyabhai 2000-04-06 16:39:59 EDT
We've verified that this is fixed in 6.2, available from our FTP site in
ftp://ftp.redhat.com/pub/redhat/redhat-6.2/i386/RedHat/RPMS/.  The key packages
are initscripts, ppp, wvdial, and rp3.

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