[Fixed in 2.5.0] Failed Palo Alto Diff

[fti-msmith]

We are still noticing an issue that I believe is a sorting issue.

Example sample below

Code: Select all

source [ 10.1.200.2 10.1.200.251 10.1.200.48 10.1.200.49 172.25.200.109 172.25.79.20 172.27.240.0/20 172.30.12.45 172.30.16.45 172.30.20.45 172.30.255.21 172.30.255.24 172.30.28.44 172.30.4.45 172.30.64.42 172.30.68.45 172.30.72.45 172.30.8.45 172.30.98.44 172.30.99.24 ];

Change detected was as follows

Code: Select all

source [ 10.1.200.2 10.1.200.251 10.1.200.48 10.1.200.49 17 172.25.79.20 172.27.240.0/20 172.30.12.45 172.30.16.45 172.30.20.45 172.30.255.21 172.30.255.24 172.30.28.44 172.30.4.45 172.30.64.42 172.30.68.45 172.30.72.45 172.30.8.45 172.30.98.44 172.30.99.24 2.25.200.109 ];

Looks like the the 5th object - 172.25.200.109 address was split with 17 separated but the remainder shows as 2.25.200.109?

[Tomas]

We are still noticing an issue that I believe is a sorting issue.

Hi, we have just released 2.5.0, which contains a fix for these Palo issues. This combined with a fix we did in 2.4 should hopefully eliminate all erroneous diffs on Palo. More info: viewtopic.php?f=3&t=1819