Bug 50906 - neat causes traceback and other fun when configuring cipe
Summary: neat causes traceback and other fun when configuring cipe
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: redhat-config-network
Version: roswell
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-08-04 18:01 UTC by Jeff Lane
Modified: 2008-05-01 15:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-08-04 18:02:44 UTC
Embargoed:


Attachments (Terms of Use)
traceback produced when trying to save network configuration in neat. (1.38 KB, text/plain)
2001-08-04 18:02 UTC, Jeff Lane
no flags Details

Description Jeff Lane 2001-08-04 18:01:31 UTC
Description of Problem:
Running neat to config network devices causes a traceback
 (attached) then other things happen (that may or may not be reproducible)

How Reproducible:
run neat from command line.  on a machine with existing cipe, and reconfig
cipe connection.  Then click the OK box to save settings...  stderr gives
traceback, and you have to cancel out of the tool to continue.  So far,
this has happened each time I have attempted this.  And each time, all I
did to edit cipe was to reverse the p-t-p and ipaddr fields.  tehn click on
OK to save.

Steps to Reproduce:
1. see above
2. 
3. 

Actual Results:
traceback that is attached.

Additional Information:
Also, on a side note, after canceling out of this, I could not ping
loopback or anything else.  ipchains -L showed NO rules at all.  then I did
a service ipchains stop, and magically, I could ping again.

Comment 1 Jeff Lane 2001-08-04 18:02:40 UTC
Created attachment 26252 [details]
traceback produced when trying to save network configuration in neat.

Comment 2 Trond Eivind Glomsrxd 2001-08-05 19:53:47 UTC
Fixed in newer releases, like redhat-config-network-0.6.4-1


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