Global Protect Agent prisma Access

[FarrasErdiansyah]

Hi, i have question. while connecting through internal connection i got ssl protocol in GP agent, but if i connected to external connection i got IPsec protocol on my GP agent. i want to ask how could i get Ipsec protocol while connected to internal connection?  my global protect already integrated to prisma access. you can see the pictures below

thanks

[nikoolayy1]

First you need to answer the question why do you need IPSEC when the internal gateway is internal because for outside connections you use Remote network (SPN) with ipsec tunnel to prisma access  as double ipsec encryption is bad news? The internal gateway is just to collect the user id and HIP data and send it in XML that could be over SSL (maybe that is what you are seeing).

Prisma Access Internal Gateway

Other than that if you are using on-prem Firewall as as internal gateway you need to select tunnel mode and enable the IPSec checkmark as I proved the link below. If IPsec is blocked the tunnel will failover to SSL so check your security policies on the NGFW and on any network devices in between. Configure the host detection as well as the NGFW to know when to switch to the internal gateway. If you reach the internal gateway Palo Alto NGFW Firewall through Prisma Access tunnel then better not configure tunnel mode , if traffic goes to prisma access after the internal NGFW gateway then there is a point doing this.

GlobalProtect Gateways

How to Confirm if GlobalProtect Tunnel is Using IPSec or SSL? - Knowledge Base - Palo Alto Networks

[Vickynet]

---

@FarrasErdiansyah wrote:

Hi, i have question. while connecting through internal connection i got ssl protocol in GP agent, but if i connected to external connection i got IPsec protocol on my GP agent. i want to ask how could i get Ipsec protocol while connected to internal connection?  my global protect already integrated to prisma access. you can see the pictures below

thanks

---

Hello @FarrasErdiansyah , I understand you're experiencing a protocol mismatch between your internal and external gateways connections. To ensure that your GlobalProtect agent uses IPsec for internal connections, you can follow these steps:

Step 1: Check Gateway Configuration: Navigate to Network > GlobalProtect > Gateways in your Prisma Access portal. Select the appropriate gateway and ensure that the "Enable IPSec" checkbox is checked. Check the "Steps from the GUI" from this documentation for reference; https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PPY1CAO 

Step 2: Verify Traffic Flow: Ensure that traffic on UDP port 4501 is not being blocked anywhere along the path. This port is used for IPsec connections.

Step 3: Debugging: You can also set the rasmgr process to debug level by running the command debug rasmgr on debug. This will generate detailed logs in the rasmgr.log file, which can help identify why the IPsec connection is not being established.

By following these steps above, you should be able to configure your GlobalProtect agent to use IPsec for internal connections. If you still encounter issues, it might be helpful to reach out to Palo Alto Networks support for further assistance.

I hope you find this helpful. 

Thank you,

Vickynet