topic Re: GP issues with MACOS Sequoia in GlobalProtect Discussions

GP issues with MACOS Sequoia

UtkarshKumar — Wed, 11 Dec 2024 01:00:29 GMT

Hello Team

We have a user who recently upgraded their MAC to OS Sequoia and since have issues browsing any website when connected to Global Protect Agent 6.2.6.

We have tried multiple browsers with no change in behavior.

++ Verified that DNS is being resolved correctly.
++ No issues if we try to ping yahoo.com using the terminal
++ Client initially downloaded 6.3.1 but since it is not compatible they have since downgraded to 6.2.6 GP agent version -- still no change in behavior.
++ There are no issues connecting to GP bit nothing works after the user is connected to GP and try to browse any website -- they have split tunneling in place but for example, yahho.com should not be routed via the Firewall and should go out directly via Client's internet.
++ Suspecting SSL to be an issue -- we checked with CURL and cannot see any issues with SSL Connection
++ Tried Chrome, Safari, and Firefox -- still no change.
++ Permissions have been given to GP on MACOS while reinstalling 6.2.6
++ Even traffic coming to the firewall is being allowed and we see no drops, the tunnel stays connected on the new MACOS.

Is there anything we can check or if anyone faced a similar issue? Not sure if this is already a known issue with newer GP versions and MAC.

Re: GP issues with MACOS Sequoia

arusharma — Wed, 11 Dec 2024 04:20:44 GMT

What type of connection you are using IPSEC or SSL? Are you using IPV6? What is the MTU set on the portal try reducing it lower value. For further clarity, we need to see the pcap when the traffic leaves the pangp interface for those websites.

Re: GP issues with MACOS Sequoia

BPry — Wed, 11 Dec 2024 22:49:15 GMT

@UtkarshKumar,

Do you know the specific version number that they're running. There were a lot of VPN issues with 15.0 proper that were somewhat helped with 15.0.1. I haven't had any issues reported on 15.1.1 or 15.2 (just released today). It kind of sounds like they may be running 15.0 where these issues were pretty common and could be fixed by disabling the macOS firewall (but now you really should just update to 15.1.1/15.2).