03-04-2020 11:34 AM - edited 03-04-2020 02:59 PM
I upgraded Expedition to version 1.1.59 and it's telling me that all of my address objects, that are set to "ip ranges", are invalid. They aren't invalid. I can add them to my Palo Alto firewall in the same format without issue. I'm unable to add address objects using the "ip range" selection. I imported a Cisco ASA config.
03-09-2020 01:16 AM
Hi,
Thanks for pointing this out.
I think this should be now corrected in 1.1.60, which we released on Thursday afternoon CET time.
We have been improving the validity controls on address objects to support IPv6, fqdn and others, and my fault, I introduced one issue when controlling the ipv4-ipv6 range.
03-04-2020 03:01 PM
Hello Rcarmack1970,
I am able to reproduce the issue as you mentioned, have escalated to developer , will get back to you.
Thank you!
Lynn
03-09-2020 01:16 AM
Hi,
Thanks for pointing this out.
I think this should be now corrected in 1.1.60, which we released on Thursday afternoon CET time.
We have been improving the validity controls on address objects to support IPv6, fqdn and others, and my fault, I introduced one issue when controlling the ipv4-ipv6 range.
03-09-2020 08:07 AM
Thanks, I upgraded to 1.1.60 and the addresses look good now.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
