Bug 17973 - isdn-config may fail to spot external agent dialling
isdn-config may fail to spot external agent dialling
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: isdn-config (Show other bugs)
7.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
:
: 17972 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-09-30 16:10 EDT by Paul Flinders
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:
Environment:
Last Closed: 2001-01-04 08:27:55 EST
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 Paul Flinders 2000-09-30 16:10:44 EDT
isdn-config fails to spot that an external agent has dialled
under the following scenario

I have two ISPs configured. Starting isdn-config and
connecting to the first works as expected.

If I now hang up using "isdnctrl hangup ippp0" from a
terminal window the fact that the link has gone down is
correctly spotted and the state goes to "offline". Re-dialling
ippp0 from the terminal is correctly tracked with the state
going to "online"

If I now manually dial my second ISP (with "isdnctrl dial ippp1")
the fact that there is an active connection is missed - the
state remains at offline.

As an aside it would be useful if isdn-config could indicate
which provider (or providers as there's no reason not to be
connected twice) are currently connected rather than just
"online" which could be any provider.
Comment 1 Ngo Than 2001-01-04 08:27:49 EST
*** Bug 17972 has been marked as a duplicate of this bug. ***
Comment 2 Ngo Than 2001-09-20 17:28:36 EDT
isdn-config is now obsolete. kisdndock is a new dial program. It's a part of
kdenetwork-2.2-x

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