Bug 111047 - RHN Systems-> Hardware -> Networking has extra 0's in ip addresses
Summary: RHN Systems-> Hardware -> Networking has extra 0's in ip addresses
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Web Site (Show other bugs)
(Show other bugs)
Version: RHN Stable
Hardware: All Linux
medium
low
Target Milestone: ---
Assignee: Mike Orazi
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-11-26 18:34 UTC by Josiah Royse
Modified: 2008-03-04 21:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-03-04 21:59:40 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Josiah Royse 2003-11-26 18:34:27 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031030

Description of problem:
The Networking section of the Hardware properties of the system has
extra 0's (Zeros) in the ip addresses/subnet masks.  It functionally
is acurate, but is confusing to read.

Version-Release number of selected component (if applicable):
up2date-3.1.23.2-1, rhnlib-1.0-4.noarch.rpm (Redhat 9)

How reproducible:
Always

Steps to Reproduce:
1.register system to RHN
2. log in to RHN website
3. check out networking properties under hardware on the system
    

Actual Results:  
Hostname:  	t-rex
IP Address: 	192.168.10.5

Interface 	IP Address 	Netmask 	Broadcast 	Hardware Address 	Driver Module
eth0 	192.168.10.05 	255.255.255.00 	192.168.10.255 
00:a0:cc:58:65:ae 	tulip
lo 	127.00.00.01 	255.00.00.00 	127.255.255.255 	00:00:00:00:00:00 
loopback

Expected Results:  examples should look like
192.168.10.5/255.255.255.0, 127.0.0.1/255.0.0.0   etc...

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