Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 102999

Summary:	ISDN connection can't be established
Product:	[Retired] Red Hat Linux	Reporter:	Lars Rohleder <redhat.ygum0>
Component:	isdn-config	Assignee:	Than Ngo <than>
Status:	CLOSED ERRATA	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	9	CC:	redhat.ygum0
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-08-27 16:43:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lars Rohleder 2003-08-24 22:32:56 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624

Description of problem:
If I got this right ISDN under linux always uses an ipppx interface to connect
to the internet (default: ippp0). Due to the fact that RedHat linux installs an
isdn card as device "isdn0" it needs to be bound to ippp0. This is done by the
command
isdnctrl pppbind isdn0
But sadly this won't work for me (and I don't know why).

As a workaround I renamed ifcfg-isdn0 to ifcfg-ippp0 and changed the DEVICE
variable to 'ippp0'. Now everything works fine but I'm not really happy with
this solution. Why not just call those interfaces ippp0?

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


How reproducible:
Always

Steps to Reproduce:
1. Use Configuration Wizard or install isdn card and device manually. The device
will be named 'isdn0'.
2. Try to activate the device through System Settings -> Network
3. You'll get an error message like "Can't find (free) connection[...]" or
something like that (didn't write the message down).

Comment 1 Lars Rohleder 2003-08-25 15:20:33 UTC

I searched american an german newsgroups on this topic and only found one
posting with the same problem. The user with the same problem uses the same
release: the RedHat 9.A which comes with the german version of the RedHat
Magazine. Maybe it's only a bug in this release? Will it be fixed in the next
german RedHat Magazine (september)?

Lars

Comment 2 Than Ngo 2003-08-27 16:43:59 UTC

it's a known bug and already fixed in redhat-config-network-1.2.15-1, which was
released as errata.