Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 88307 - Unable to save hardware address using neat tool
Unable to save hardware address using neat tool
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: redhat-config-network (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Depends On:
  Show dependency treegraph
Reported: 2003-04-08 15:37 EDT by William Keeling
Modified: 2007-11-30 17:06 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-04-17 11:47:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
dump from neat (1.14 KB, text/plain)
2003-04-08 15:41 EDT, William Keeling
no flags Details

  None (edit)
Description William Keeling 2003-04-08 15:37:27 EDT
Description of problem:
Unable to save hardware address using neat tool

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

How reproducible: every time

Steps to Reproduce:
1.run neat
2.select device and click edit
3.select use hardware address and click probe for address and ok
4 click apply 
Actual results:
see attached dump file

Expected results:
to save hardware address

Additional info:
no other changes made using neat have worked
Comment 1 William Keeling 2003-04-08 15:41:18 EDT
Created attachment 91012 [details]
dump from neat
Comment 2 Harald Hoyer 2003-04-09 08:15:06 EDT
which version? did you use the errata?
Comment 3 William Keeling 2003-04-09 20:14:39 EDT
Comment 4 Harald Hoyer 2003-04-17 06:43:11 EDT
$ rpm -q redhat-config-network
should show: redhat-config-network-1.0.4-0.AS21.1
Comment 5 William Keeling 2003-04-17 11:37:33 EDT
Sorry -- I thought you wanted the kernel version. 

network config tool was at redhat-config-network-0.9.10-2.1 I installed the new 
package 1.0.4-0.AS21.1 and the problem is fixed.


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