I recently moved a firewall into being managed by Panorama. I setup an Application rule specifying the application as PANORAMA which includes the ports necessary (I assumed) for Panorama communications but the firewall could not be added successfully until I allowed port 3978 traffic.
The logs showed 3978 being recognized as SSL initially and being denied as it wasn't getting included in the rule. What I don't understand or I guess I misunderstand, why isn't SSL allowed under that rule until the service is recognized as Panorama? SSL is implicitly allowed under the PANORAMA application so I thought it was allowed initially under that rule on the ports the application supports.
What am I missing?
I thought I understood it based on this article but this isn't how it seems to be working:
Hi @TonyDeHart ,
I googled PAN-192930 and found it "addressed" (fixed) in 10.1.6 and 10.2.2.
Sorry I guess I could have done that... Thank you!
So now the only problem is we are running 10.2.3-h4 and 10.1.9-h1 and that doesn't work. Not sure what is fixed unless the discussion the engineer pointed out was related to this "fix" not actually being fixed.
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!