Globalprotect terminating in its own vsys?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Globalprotect terminating in its own vsys?

Not applicable

I'm trying to setup GlobalProtect to terminate in its own VSYS (for administrative purposes), i.e the Portal and Gateway should reside in its own VSYS and not in my external vsys.

But I would like to be able to use the same physical interface as the external vsys, is that even possible?

I have tried to create a loopback interface with its own external IP (no nat), and tied it to the portal and gateway.

Intra vsys routing is setup, and security policies are setup.

But I can't access the portal on port 443 from Internet. I see the traffic coming in in my external vsys, and that it is routed to my GP-vsys on the loopback interface. But the GP-vsys don't show anything in the traffic log, and I don't get any response back.

Has anyone setup globalprotect in its own vsys, where traffic are routed through the external vsys? Is that possible?

Panos 5.0.11

1 accepted solution

Accepted Solutions

Not applicable

Problem solved.

I needed to setup a shared gateway with the external interface to get it to work properly.

View solution in original post

1 REPLY 1

Not applicable

Problem solved.

I needed to setup a shared gateway with the external interface to get it to work properly.

  • 1 accepted solution
  • 1891 Views
  • 1 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!