Bug 55083 - Upgrade from Red Hat Linux v7.1 to v7.2 doesn't keep ISDN configuration
Summary: Upgrade from Red Hat Linux v7.1 to v7.2 doesn't keep ISDN configuration
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: isdn-config
Version: 7.2
Hardware: athlon
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-10-25 10:12 UTC by André Johansen
Modified: 2007-04-18 16:37 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-10-25 18:04:10 UTC
Embargoed:


Attachments (Terms of Use)

Description André Johansen 2001-10-25 10:12:26 UTC
When installing v7.1, configuring the ISDN system was a breeze using the
"isdn-config" tool.

After the upgrade, this program seems to have been replaced with "neat",
which is unable to reactivate the old configuration.

(I'll try to add more specifics when I have access to the machine again.)

Comment 1 Ngo Than 2001-10-25 10:35:00 UTC
Do you see your ISDN configuration, if you start neat ?
please check in /etc/sysconfig/network-scripts/, the ifcfg-ipppX should exists.

to start or stop ISDN you should use ifup or iifdown pppX (X is 0 if you only
have a ISDN configuration).

Comment 2 André Johansen 2001-10-25 11:15:06 UTC
Yes, I can see it (named "WorldOnline", as I named it in the old program).

I'll check the availability of the scripts when I have access to the machine
again.

In Red Hat Linux v7.1, "service {isdn,network} start" was sufficient to start
the ISDN system.



Comment 3 André Johansen 2001-10-25 18:04:02 UTC
By deleting the old device from neat, neat somehow recreated it on the next
startup, and I am now able to connect to the Internet using my ISDN card
and kisdndock.

The major problem is thus solved, but the fact still remains that it did not
automatically work with the old configuration.  Not a major problem,
but annoying.



Comment 4 Ngo Than 2001-10-29 22:15:34 UTC
It's fixed in isdn4k-utils-3.1-47. You find it on ftp://people.redhat.com/than/7.2


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