Globalprotect terminating in its own vsys?

HansH — Fri, 14 Feb 2014 14:02:03 GMT

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

Re: Globalprotect terminating in its own vsys?

HansH — Thu, 08 May 2014 07:19:56 GMT

Problem solved.

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

topic Globalprotect terminating in its own vsys? in General Topics

Globalprotect terminating in its own vsys?

Re: Globalprotect terminating in its own vsys?