Bug 58460

Summary:	neat ippp slave assignment
Product:	[Retired] Red Hat Linux	Reporter:	Andreas Mack <andreas.mack>
Component:	redhat-config-network	Assignee:	Than Ngo <than>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	7.2	CC:	andreas.mack, harald, jrb, pknirsch, teg
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:	2002-02-20 16:13:00 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 Andreas Mack 2002-01-17 09:05:55 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.6) Gecko/20011120

Description of problem:
If you have several isdn devices configured and decide to put ippp0
to do channel-bundling, neat chooses ippp1 as slave, which is in use.
ippp0 is unusable then, syslog says "ippp1 in use".

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


How reproducible:
Always

Steps to Reproduce:
1.create ippp0
2.create ippp1, different phone# etc
3.save
4.put ippp0 in channel-bundling mode
5.dial ippp0
	

Actual Results:  ippp0 is unusable then, syslog says "ippp1 in use".

Expected Results:  ippp0 should do channel-bundling

Additional info:

work-around: edit ifcfg-ippp0, last line, but neat will overwrite it
next time. :/

Comment 1 Ngo Than 2002-04-13 12:09:07 UTC

it's fixed in redhat-config-network-0.9.25-1