FW Policy Skipped When Either App-Based only or SMTP-BASE app and 587 Port is Defined

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

FW Policy Skipped When Either App-Based only or SMTP-BASE app and 587 Port is Defined

L1 Bithead

Firewall is skipping policy when the traffic has smtp-base port 587 on it. 

I created a firewall policy application based with smtp-base as application but it skips the policy goes to the implicit interzone deny policy. So I created it with by just port based, 587, it sill skips the policy and goes to interzone default deny. 

So I explicitly defined app-based and port based on the policy, it still skips the policy. 

When I run the troubleshooter, Test Policy, it is able to match the policy created when I only specified the port 587. It skips it when I add the application, smtp-base. 

PA-440, PANOS 10.1.9

Anyone else encountered the same issue and was able to solve it? Or anything you recommend to solve this is greatly appreciated!

4 REPLIES 4

Community Team Member

Hi @EmmanB-NC ,

 

Strange. It would be interesting to see the full configuration of the rules in question and compare it to the deny rule.

When you're hitting the default-deny rules, how is the traffic being identified exactly ? 

 

Kind regards,

-Kim.

LIVEcommunity team member, CISSP
Cheers,
Kiwi
Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.

Hi Kiwi, 

It turned out the application recognized to destination smtp.office365.com is outlook-web-online using port 587 and not smtp-base. This is when I enabled Any Any temporarily to see what application traffic is actually going over the firewall. 
Traffic appears to be allowed on the firewall however email is not received by expected recipient. 

Community Team Member

Hi @EmmanB-NC ,

 

Because that FQDN destination is changing IP every few seconds I believe you might be hitting the following issue:
Using FQDN address object with dynamic IP for Policies 

 

Hope this helps,

-Kim.

LIVEcommunity team member, CISSP
Cheers,
Kiwi
Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.

I tried it also with the actual IP range object defined on the policy. It appears as allowed traffic but the application still gets an error. 

  • 1091 Views
  • 4 replies
  • 0 Likes
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!