Bug 14859 - ppp0 manual redialing problems
ppp0 manual redialing problems
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
6.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-07-30 16:15 EDT by Bryan Reece
Modified: 2014-03-16 22:15 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-07-30 16:15:05 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Bryan Reece 2000-07-30 16:15:02 EDT
If a user issues `ifup ppp0' while the link is already up, the script saya
 ppp0 already up, initiating redial
and starts the advertised redial.  Subsequent `ifdown ppp0' commands fail
due to the absence of /var/run/pppwatch-ppp0.pid, and manual intervention
is required.

Redialing doesn't drop the line for long, so the first redial attempt gets
the `If you'd like to make a call, please hang up and try again' that the
local switch sends if you stay off-hook after the distant party hangs up.

Attempting to force a second redial manually (another `ifup ppp0' shortly
after the failed call attempt) seems to result in dueling chats: 
one chat sends a dial command, then the second sends a dial command that
aborts the first dial, causing someone to see `NO CARRIER' and retry ad
nauseam.
Comment 1 Bill Nottingham 2000-08-07 01:24:49 EDT
This has since been fixed; subsequent ppp-watch calls do
not kill the first ppp-watch's lock file.

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