Description of problem: Using netmasks is cumbersome: they're much longer and harder to remember as opposed to corresponding network prefix. The correct prefix can not be interchanged with correct netmask, conversion is quite straightforward and newer low-level tools work with prefixes natively. Therefore I propose the "Netmask" fields (and appropriate places in API) to have their heading changed to "Netmask/Prefix" and have them accept integers in 0-32 range as correct prefix values. This is IMO quite a small change nice leap forward in convenience in environments with statically assigned IP configuration. Version-Release number of selected component (if applicable): RHEV 3.3. How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Hi Eliraz, I have a question with regards to the implementation of this; currently there is a netmask field in which the user should enter the subnet mask in dot-decimal notation (x.x.x.x). With this change, are we going to change that and only accept CIDR notation (/xx)? Or the user can fill the info in either way (dot-decimal or CIDR)? Thanks, Nir
The current design is to accept either, but always report in dot-decimal format.
Verified on - 3.6.0-0.0.master.20150412172306.git55ba764.el6 with vdsm-4.17.0-632.git19a83a2.el7.x86_64
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-0376.html