Bug 207845
| Summary: | Anaconda netmask editting does not work | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Jos Vos <jos> |
| Component: | anaconda | Assignee: | Dave Cantrell <dcantrell> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike McLean <mikem> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.0 | CC: | 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
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. 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. CIDR prefix to netmask calculation has been fixed in rawhide. Thanks. 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. (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. These problems are fixed in today's rawhide (20051004). Closing out. |