engine address parsing issue with negation
Address [192.168.0.0/16,!192.168.1.0/24,192.168.1.1] is parsed as
192.168.0.0 - 192.168.0.255, 192.168.2.0-192.168.255.255
192.168.0.0 - 192.168.0.255, 192.168.1.1 - 192.168.1.1, 192.168.2.0 - 192.168.255.255
Issue comes up when negated addresses are mixed with non-negated addresses.
Updated by Philippe Antoine about 2 months ago
That would make the list order dependent which is not the case right now.
So, I do not know if the expected behavior will be clear to everyone.
Should we go for another syntax like
(192.168.0.0/16 - 192.168.1.0/24) + 192.168.1.1
Then we should issue warnings when we do not have enough parenthesis as operations are not commutative...