Bug 58460 - neat ippp slave assignment
Summary: neat ippp slave assignment
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network
Version: 7.2
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Than Ngo
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-01-17 09:05 UTC by andreas.mack@konsec.com
Modified: 2008-05-01 15:38 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-02-20 16:13:00 UTC
Embargoed:


Attachments (Terms of Use)

Description andreas.mack@konsec.com 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


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