Description of problem: It would be nice if we could use the standard CIDR format (192.168.1.0/24) when setting auth.allow and auth.reject to a volume. Right now, only 192.168.1.* is supported. That's fine for a /16 or /24, but what if I use a /23? Then I need to add several entries. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: gluster volume set test auth.allow 192.168.1.0/23 Actual results: [root@node6 ~]# gluster volume set test auth.allow 192.168.1.0/24 volume set: failed: option auth.addr./volumes/test.allow 192.168.1.0/24: '192.168.1.0/24' is not a valid internet-address-list Expected results: I'd expect gluster to be able to handle the CIDR format. Actually very surprised it doesn't. Additional info:
Feature requests make most sense against the 'mainline' release, there is no ETA for an implementation and requests might get forgotten when filed against a particular version.
Four years and this feature is not yet implemented. It's impossible to bind volumes to specific networks without CIDR. Octet wildcards * are useless since classess routing has been introduced (long time ago).
Migrated to github: https://github.com/gluster/glusterfs/issues/589 Please follow the github issue for further updates on this bug.
REVIEW: https://review.gluster.org/21970 (Added a function to validate CIDR IP) posted (#1) for review on master by Rinku Kothiya
REVIEW: https://review.gluster.org/21980 (Modified few functions to isolate cidr feature) posted (#1) for review on master by Rinku Kothiya
REVIEW: https://review.gluster.org/21970 (core: Feature added to accept CidrIp in auth.allow) merged (#10) on master by Amar Tumballi
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report. glusterfs-6.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2019-March/000120.html [2] https://www.gluster.org/pipermail/gluster-users/