Re: Firewall address range address book objects appearing as address sets with individual objects mem0,1,2 etc

Hi PK,

I have copied an example from our config for reference, I created the object as you did in the labs via cli and it appeared in the config as expected, of note we use Junosd Space to create object and apply policy and from some more testing it looks like it's Space that's applying this config, I created the object using Space to be used in a dummy rule and copied the config changes it expected to make which shows the creation of the objects and address set?

So it looks like Space is appying this config for the range object, we can't recall this always being the case, past config versions show the same config but Space may have altered these at some point, it looks odd to us and unexpected.

Example of expected range object from current config:-

address-book {
address radiotherapy-deny-web-access-10.243.3.101-103-mem0 10.243.3.101/32;
address radiotherapy-deny-web-access-10.243.3.101-103-mem1 10.243.3.102/31;

address-set radiotherapy-deny-web-access-10.243.3.101-103 {
description "deny web access to range of ips";
address radiotherapy-deny-web-access-10.243.3.101-103-mem0;
address radiotherapy-deny-web-access-10.243.3.101-103-mem1;

Test object created via Cli, format as expected:-

address device-10.1.1.101-103 {
range-address 10.1.1.101 {
to {
10.1.1.103;
}
}
}

Config to be applied from Space for the creation of the same range object:-

set security zones security-zone others address-book address device-10.1.1.101-103-mem0 10.1.1.101/32
set security zones security-zone others address-book address device-10.1.1.101-103-mem1 10.1.1.102/31
set security zones security-zone others address-book address-set device-10.1.1.101-103 address device-10.1.1.101-103-mem0
set security zones security-zone others address-book address-set device-10.1.1.101-103 address device-10.1.1.101-103-mem1