Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 69569

Summary:	RFE: Better config for isdn* vs. ippp* devices
Product:	[Retired] Red Hat Linux	Reporter:	Bernd Bartmann <bernd.bartmann>
Component:	redhat-config-network	Assignee:	Than Ngo <than>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0	CC:	harald, teg
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-08-04 20:10:28 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:
Bug Depends On:
Bug Blocks:	81720

Description Bernd Bartmann 2002-07-23 10:32:56 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
Right now it is impossible to create an rawip/hdlc isdn connection using 
neat's isdn config wizard. A new isdn connection is always set to use syncppp. 
For rawip/hdlc username/password also don't make any sense.

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


How reproducible:
Always

Steps to Reproduce:
1. Try a create a new rawip/hdlc isdn connection using neat's isdn wizard.
2.
3.
	

Additional info:

Comment 1 Harald Hoyer 2003-01-13 11:33:49 UTC

will be in >= 1.1.87..

Comment 2 Bill Nottingham 2006-08-04 20:10:28 UTC

Red Hat Linux and Red Hat Powertools are currently no longer supported by Red
Hat, Inc. In an effort to clean up bugzilla, we are closing all bugs in MODIFIED
state for these products.

However, we do want to make sure that nothing important slips through the
cracks. If, in fact, these issues are not resolved in a current Fedora Core
Release (such as Fedora Core 5), please open a new issues stating so. Thanks.