Mobile user Protocol

[DickyAnggara]

We have sase prism and have deployed it for mobile users. Currently the mobile user is running, but I have a concert about the protocol used. So when we use private hotspot tathering the protocol used is ipsec, but when we use the internal protocol used is ssl, in the gp config we have enforced for vpn to only use ipsec but still use ssl when using an internal connection. So do you need to check again?

Fyi On the firewall there is no blocking for the ipsec port

[Vickynet]

---

@DickyAnggara wrote:

We have sase prism and have deployed it for mobile users. Currently the mobile user is running, but I have a concert about the protocol used. So when we use private hotspot tathering the protocol used is ipsec, but when we use the internal protocol used is ssl, in the gp config we have enforced for vpn to only use ipsec but still use ssl when using an internal connection. So do you need to check again?

Fyi On the firewall there is no blocking for the ipsec port

---

---

@DickyAnggara wrote:

We have sase prism and have deployed it for mobile users. Currently the mobile user is running, but I have a concert about the protocol used. So when we use private hotspot tathering the protocol used is ipsec, but when we use the internal protocol used is ssl, in the gp config we have enforced for vpn to only use ipsec but still use ssl when using an internal connection. So do you need to check again?

Fyi On the firewall there is no blocking for the ipsec port

---

Hello @DickyAnggara,  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, here are the steps I would recommend to check again; 

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