ASA Migration - TCP/UDP source port rules not migrated

cancel
Showing results for 
Search instead for 
Did you mean: 

ASA Migration - TCP/UDP source port rules not migrated

L2 Linker

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

1 ACCEPTED SOLUTION

Accepted Solutions

L4 Transporter

Not currently supported. Will add a feature request for this. 

View solution in original post

2 REPLIES 2

L4 Transporter

Not currently supported. Will add a feature request for this. 

Is there a solution to work around this in Expedition? I am also experiencing this issue

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!