Disable SSL - IPSEC only

[Hithead]

Hi,

a quick one: is it possible to disable SSL VPN at GP? So users can only connect via IPSEC...

I know its possible to do it the other way but we like to have a IPSEC only portal/gateway.

[hshah]

Hello HitHead,

Portal runs on SSL, but you can configure gateway for IPsec. Please configure following settings on Gateway for IPsec.

Regards,

Hardik Shah

[Hithead]

thanks,

I know, but the failover mechanism is still active (if IPSEC fails, GP is trying to connect via SSL).

[hshah]

Hi Hithead,

Than you can block SSL for Gateway IP address in Policy. That way failover will not take place in reality.

This will work only if portal is on another firewall.

Regards,

Hardik Shah

[hshah]

Hi Hithead,

Let me know if this helps, there is no inbuilt way or command to disable SSL.

I didnt find any existing Feature Request to disable SSL, I would suggest to contact Sales Engineer to open new Feature Request.

Regards,

Hardik Shah

[Hithead]

Hi hshah,

Portal = Gateway in our installations. So not possible.

Will contact SE for a feature request. Thanks.

[panos]

only way for now, just to create GP , GW config(empty portal config) and make clients connect with cisco client,ort etc.instead of GP client.

[hshah]

Hi HitHead,

In that case you can assign loopback IP to Portal and loopback should be part of untrust network.

Now you car restrict traffic on Gateway.

Let me know if thats a good work around.

Regards,

Hardik Shah

[Hithead]

sorry but how should that work?

(We have one public IP (gateway = portal) NATed to the Portal. At the Portal we configured the public DNS as gateway for the client config.)

[HULK]

Do you have any free public IP from the pool. That can be configured on Loopback.

Thanks

[Hithead]

No sadly not.

But I really like to know, how the loopback config works...

As I know, we have to authenticate at the Portal and Gateway with SSL (client certificate authentication). So I have to open (and NAT) SSL to the Portal/Gateway IP (IP is the same; private range).

So, and if the Portal IP is the loopback interface in a untrusted zone and my client gets the IP or DNS name of the gateway from the portal, SSL is still required for the authentication at the gateway. SSL is still open. - Hope its clear enough...? Understood my concern?

THX

[HULK]

Split and Full Tunnel in GlobalProtect Causes Users to Connect Through SSL on Loopback

Thanks

[Hithead]

HULK,

your answer is helpful but please correct me if I'm wrong or misunderstand the configuration:

Fist, a citation: " This request can be received either by Split tunnel on the physical interface ethernet 1/1, or by Full tunnel on the loopback interface by NATing 88.88.88.88:4501 to 1.1.1.1:4501. Both Split and Full tunnel cannot receive the IPSec request."

If I will configure our Portal/Gateway with the loopback solution, the authentication against the gateway is still necessary with SSL (port doesn't matter). Ok, my clients will connect with IPSEC but the SSL failover mechanism configured at the agent is still enable and also possible, because you have to authenticate against the gateway with SSL.

So in my opinion there is no way to disable a SSL tunnel, because of the SSL failover mechanism and authentication against the gateway.

Please correct me, if I'm wrong!