Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 207845

Summary: Anaconda netmask editting does not work
Product: Red Hat Enterprise Linux 5 Reporter: Jos Vos <jos>
Component: anacondaAssignee: Dave Cantrell <dcantrell>
Status: CLOSED CURRENTRELEASE QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0CC: notting
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 5.0.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-02-14 19:41:17 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:
Bug Depends On:    
Bug Blocks: 150224    

Description Jos Vos 2006-09-24 15:56:32 UTC
Description of problem:
When editting interface info in the graphical interface, the "Netmask" field
only seems to accept a subset of possible netmasks, e.g. it accepts
255.255.255.0, but not 255.255.255.240 or 255.255.255.248.

How reproducable:
Choose "edit" for a network interface in the graphical installer.

Further comments:
Specifying a netmask in the text interface (after the / of in the IP address
field), before the graphical installer starts (after choosing NFS install) works
fine, it accepts all netmasks I tried and it even plain numbers, like "24" or
"28", which is a good thing.

Comment 1 Dave Cantrell 2006-09-25 17:35:39 UTC
This has been fixed in rawhide and will make its way in to the next RHEL5 beta
or alpha or test release.

Netmasks and CIDR-prefixes are accepted for the IPv4 prefix.

Comment 2 Bill Nottingham 2006-09-27 22:08:48 UTC
With rawhide-20060927, this is still broken.

If I enter 172.16.56.125/22, it gives me a netmask of 255.255.63.0 (instead of
255.255.252.0).

If I enter 172.16.56.125/255.255.252.0, it gives me a prefix of /24.



Comment 3 Dave Cantrell 2006-10-02 19:32:43 UTC
CIDR prefix to netmask calculation has been fixed in rawhide.  Thanks.

Comment 4 Bill Nottingham 2006-10-03 16:23:01 UTC
If I enter 172.16.56.125/22, while it does calculate the netmask correctly, it
displays in the 'Network Devices dialog' as 172.16.56.125/24.

Comment 5 Dave Cantrell 2006-10-03 19:03:02 UTC
(In reply to comment #4)
> If I enter 172.16.56.125/22, while it does calculate the netmask correctly, it
> displays in the 'Network Devices dialog' as 172.16.56.125/24.

Seriously, notting...are you never satisfied?  I fixed this exact problem about
5 minutes ago and committed it to HEAD for rawhide.

It was just a display issue, the internal values were still correct.

BUT, I did just uncover another problem.  The input validation code is borken on
big endian systems.  Working on that.

Comment 6 Dave Cantrell 2006-10-04 17:23:15 UTC
These problems are fixed in today's rawhide (20051004).

Comment 7 Jay Turner 2007-02-14 19:41:17 UTC
Closing out.