On 02/15/2012 10:26 AM, Nicolas Charles wrote: > Oh yes, I've been overcomplexifying with the ipv4 prefix, thank you Nick > But I feel the iprange function more usable in case of complex architecture
I should finish reading things, thats very nice, I didn't know that function existed and i missed it in your first email, thanks for pointing it out again, this will help me a lot. I just commented on a feature request the other day that it would be nice to have cidr classes defined. https://cfengine.com/bugtracker/view.php?id=858 It would also be nice to have a hard class for the cidr network. The case where you have multiple networks on a machine with multiple netmasks being able to easily identify the specific networks that exist instead of just a list of netmasks and ips where you have to do mixing and matching. Perhaps in the form cidr_network_mask Consider a host with the following interfaces 10.0.0.10 netmask 255.255.255.240 172.16.0.5 netmask 255.255.255.240 172.16.0.35 netmask 255.255.255.240 The following additional hard classes could be defined cidr_10_0_0_0_28 cidr_172_16_0_0_28 cidr_172_16_0_32_28 That would allow precise network identification Along with that I suppose sys.cidr would be handy and given the above example would contain 10.0.0.0/28 172.16.0.0/28 172.16.0.32/28 _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
