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 112649 - ISDN interface (ippp0 device): unable to deactivate it
ISDN interface (ippp0 device): unable to deactivate it
Status: CLOSED DUPLICATE of bug 112194
Product: Fedora
Classification: Fedora
Component: redhat-config-network (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Depends On:
  Show dependency treegraph
Reported: 2003-12-26 04:59 EST by Francesco Parisi
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:00:30 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 Francesco Parisi 2003-12-26 04:59:12 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; it-IT; rv:1.4.1)

Description of problem:
Once activated the ISDN interface is impossible to deactivate it: the
button "Deactive" isn't enabled and the status of interface is always

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Launch redhat-config-network from a X console
2.Select ISDN interface (previuos configured) then press button
"Active" ("Attiva" in italian language)
3.Interface became active
4.Button "Deactive" isn't functionally
5.Interface status (device ippp0) is always "Deactive"

Additional info:
Comment 1 Neil Drinkwater 2004-01-20 00:46:12 EST
This bug is similar if not the same for device ppp0. The device is 
activated, but R-C-N still shows "inactive", therefore cannot 
Comment 2 Harald Hoyer 2004-01-29 09:50:00 EST
try to rename the nickname to ippp0
Comment 3 Jef Spaleta 2004-01-30 23:41:48 EST

*** This bug has been marked as a duplicate of 112194 ***
Comment 4 Red Hat Bugzilla 2006-02-21 14:00:30 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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