GlobalProtect clients experiencing latency delays

[Farzana]

Hello,

Clients who are connected via GlobalProtect VPN are experiencing slowness with all their traffic traversing the VPN (ie.. Internet and Server access traffic).

The latency is between 200-400ms for all the traffic regardless of whether its Internet based (to google) or server based (to our corporate servers).

Can you suggest any troubleshooting steps for this? Any relevant article to check?

Thanks in advance.

[Raido · Accepted solution]

In GlobalProtect client, Details tab.

Check if protocol is SSL or IPSec.

If it is SSL then check if you permit udp 4501 towards GlobalProtect gateway.

Also check that you have "Enable IPSec" checked in GlobalProtect gateway config (Tunnel Settings tab).

[jdprovine]

@Raido

So you mean to permit udp 4501 in to the firewall using a security policy permiting it?  I have a rule coming in to the firewall for the global protect client  that has service any and I still get complaints from users that it still too slow.

I looked in network/interfaces/tunnel and I don't see a place in enable ipsec but I do see it enabled when I go to the globalprotect gateway configuration

[Raido]

If you run GlobalProtect on your untrust interface and you don't have block any-any rule added then last interzone-default will permit from untrust to untrust 4501.

If you run GlobalProtect gateway on loopback and then you need to NAT udp 4501 to this loopback.

GlobalProtect agent will try IPSec 3 times and then falls back to SSL.

In case SSL it is TCP inside TCP (tcp meltdown and other issues can occure).

Enable IPSec is in firewall.

[Raido]

If agent view shows IPSec then issue is somewhere else.

[jdprovine]

@Raido

Yes I have IPSEC enabled in the location in your screenshot.  I am using the SSL protocol to connect.  I must add I did not do the original configuration of the VPN's I have got them to work and now I am working at getting them to work as efficiently as I can.

I didn't find any NATTING concerning the loopbacks used for the VPN's

[Raido]

If GP agent shows SSL as protocol it can't connect with IPSec.

Go to Monitor > Traffic and use filter below.

( port.dst eq 4501 )

Do you see it being blocked?

[jdprovine]

@Raido

Port 4501 is not being blocked for legitimate traffic to the loopback for the VPN

[Raido]

Earlier you mentioned you saw no natting but now you mention that GP runs on loopback.

If it runs on loopback there must be DNAT in place.

[jdprovine]

@Raido

Good point I will check again on the natting