11-05-2018 08:34 PM
Noticed that many rules with source ports defined are not migrated over.
Instead, it creates a service only for the destination port/range and allows all ports through.
Below are a few rules. Is it a known behavior?
The first two allowed all udp and tcp ports > 1023
The third rule allowed all TCP ports
access-list OUT2IN extended permit udp any4 eq domain any4 gt 1023
access-list OUT2IN extended permit tcp any4 eq ftp-data any4 gt 1023
access-list OUT2IN extended permit tcp any4 eq ftp-data any4
Not currently supported. Will add a feature request for this.
11-07-2018 07:12 AM
Is there a solution to work around this in Expedition? I am also experiencing this issue
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!